> The fact is a similar problem is happening with the mm module, > but here I can't insert error_log to be sure... is this session > handler "race safe" ? Nope. > And I'm surprised that this concurrency issue has to be solved > on a per handler basis : isn't it functionnality duplication ? > isn't this a tricky trap for handler programmers ? is this > mentionned in the documentation ? Locking a record in your database is not duplication of functionality. - 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
- Re: [PHP-DEV] Bug #12267: Session (concurrency ?) pro... Sascha Schumann
- [PHP-DEV] Bug #12267 Updated: Session (concurrency ?)... thomas . morin
- [PHP-DEV] Bug #12267 Updated: Session (concurrenc... 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