No, that's up to you, when you construct sess_id from user name, time or such stuff...
I'v never wrote that I don't use CPAN, and if you want, you can see my preference of short own code rather than some module stupid, I see the same as independancy.
The probability of collisions when my id's are generated is, I know, but it is theoretical when more than 10 character length used. But if you check it against sessions in db when created, your action is the same as when checking the same session id given from the next request of the logged user. I cannot see relevant slowdown...
I know that I am not perfect and my solutions really contains bugs, but somebody can be interested in.
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.