Actually it will work for regular CGI as well. The usecs won't hurt anything at all. I just decided to add it as an extra precaution because I do CGI and mod_perl.
For what you are doing, I would
1. If the user doesn't have a sessionID cookie generate
a sessionID for the user and set the cookie with the sessionID
2. Use this as the file name. (Make sure to use Taint and check the sessionID for naughty characters.)
3. Open the sessionID named file and read/store you data.
4. Write a script to clean up old files and throw it in cron.
If you are really worried about filename collisions, write the files to a directory only used by this program.
-Lee
"To be civilized is to deny one's nature."
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.