in reply to Adding a bit of security to Cache::FileCache

My main concern is intentional collisions done by creating a separate script that writes to the same namespace.

I'm terribly sorry but I also should have mentioned in my original post that this is running on a ActiveState Win32 system.

-Nitrox

  • Comment on Re: Adding a bit of security to Cache::FileCache

Replies are listed 'Best First'.
Re: Re: Adding a bit of security to Cache::FileCache
by PodMaster (Abbot) on Aug 10, 2002 at 09:52 UTC
    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.

[reply]

In Section Seekers of Perl Wisdom