I keep a unique 'filestamp' in the database under each customer-- a 32-digit
randomly-generated number that then can be used either as a part of image
filenames, or as a directory name which contains a customer's images.
That way, in order for one customer to see another's images, they'd
I'm afraid I'm not familiar (although aware of) Mason, so I can't help
you in that context. I wrote something similar a while ago. When a user
uploads the image file it goes into a common directory that contains all
images. The file name is renamed to the following format:
image file checksum in
will trillich [EMAIL PROTECTED] writes:
i'm sure there's more than one way to do this -- and before i
take the likely-to-be-most-circuituitous route, i thought i'd
cull advice from the clever minds on this list...
Take a look at the mod_rewrite cookbook...there's some neat stuff in
there.
y'all seem to have some clever brains out here, so i'm wondering
if some of you can offer suggestions--
what's a good clean way to keep images private per customer?
i'm using mod_perl and HTML::Mason with session cookies, but
coming up with a paradigm for storing and revealing images
privately
