Why would you want to create a separate script that writes to the same namespace?
Just don't do it, or write to a unique namespace.
So what's it matter if information gets overwritten (what are you using this for, caching or what)?
Don't confuse FileCache with a database. It's used for caching/sharing data.
or use a nice flocking scheme if you can, or even a simple semaphore based solution separate from the FileCache module
or better yet, why
don't you (or we, i'll help)
create a Cache::FileCache::FLOCKED
which does simple semaphore based flock'ing?
um, forget that. If you're getting collisions, prevent them. Make your keys sufficiently unique (appending time() works well). Just what exactly are you storing there?
____________________________________________________
** The Third rule of perl club is a statement of fact: pod is sexy. | 