The Ids are the ones php provides, not a serial/auto_incremented primary key. in php 5 these can be computed withmd5 or sha1. see http://php.net/session specificallysession.hash_function configuration setting.. also check session.hash_bits_per_character which needs to be considered when making your tables id column width. Thus the probability for a collision of session ids is the same with file or db session handling... Thanks, Jordan
He that teaches himself hath a fool for his master. -- Benjamin Franklin Poor is the pupil who does not surpass his master. -- Leonardo da Vinci. ----- Original Message ---- From: thurting <[EMAIL PROTECTED]> To: [email protected] Sent: Thursday, March 13, 2008 5:32:48 PM Subject: Re: [fw-general] Zend_Session_SaveHandler_DbTable Is there any threat of session ids overlapping? I'm not 100% sure, but if you were to reboot your server, wouldn't the possibility exist that a user could be assigned a sid that exists in the table and is valid? Maybe not. I don't know the details of how a sid is calculated. Jordan Raub wrote: > > http://framework.zend.com/issues/browse/ZF-2335 > > Finally got around to finishing the unit tests and writing some > documentation.. I'm not done with the docs but its a decent start. The > unit tests have 94% code coverage by line count and 100% of methods. Might > be too late for 1.5.0 (maybe not?) > > Thanks, > Jordan > > He that teaches himself hath a fool for his master. -- Benjamin Franklin > Poor is the pupil who does not surpass his master. -- Leonardo da Vinci. > > > > > -- View this message in context: http://www.nabble.com/Zend_Session_SaveHandler_DbTable-tp16020268s16154p16041898.html Sent from the Zend Framework mailing list archive at Nabble.com.
