> This "solved" the problem and I concluded the bug was only due to my fault > : I should have locked my session table (or row...) to avoid race > conditions and concurrency problems. That is right. The session storage handlers have to perform locking themselves, if they are supposed to be suited for concurrent accesses. - Sascha Experience IRCG http://schumann.cx/ http://schumann.cx/ircg -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
- [PHP-DEV] Bug #12267: Session (concurrency ?) problem thomas . morin
- [PHP-DEV] Bug #12267 Updated: Session (concurrency ?)... thomas . morin
- [PHP-DEV] Bug #12267 Updated: Session (concurrency ?)... Sascha Schumann
- [PHP-DEV] Bug #12267 Updated: Session (concurrency ?)... thomas . morin
- Re: [PHP-DEV] Bug #12267 Updated: Session (concur... Sascha Schumann
- [PHP-DEV] Bug #12267 Updated: Session (concurrency ?)... kalowsky
- [PHP-DEV] Bug #12267 Updated: Session (concurrency ?)... thomas . morin
- Re: [PHP-DEV] Bug #12267 Updated: Session (concur... Sascha Schumann
- Re: [PHP-DEV] Bug #12267 Updated: Session (co... Thomas Morin
- Re: [PHP-DEV] Bug #12267 Updated: Session (co... Thomas Morin
- [PHP-DEV] Bug #12267 Updated: Session (concurrency ?)... kalowsky