Tickets :: Comment on [#7712] Memcache Session handler, shouldn't unlock if no data in memcache

* Your Email Address
* Spam protection	Enter the letters below: .__ . .. .._.. . [__)\|\ \|\| \| \| \|__\| [__)\| \\|\|__\|_\|_\| \|
Comment	>> Now, the issue is if two requests happen to occur around the same > >> time when there is no session data (ie.. expired) then there is a > >> high probability that they will overwrite each other. > >> > >> Example > >> Req 1> New Request > >> Req 1> Fetch Session (no data, expired, release lock) > >> Req 2> New Request > >> Req 2> Fetch Session (No data, expired, release lock) > >> Req 2> Processing > >> Req 2> Store Session > >> Req 2> End Request > >> Req 1> Store Session > >> Req 1> End Request > >> > >> Because there is no lock, Req 1 overwrites Req 2s data (and Req 2 is > >> allowed to actually run even though it should have waited for Req 1). > > > > Not understanding your concern clearly. Is it a duplicate of this: > > http://marc.info/?l=horde&m=122660520206201&w=2 > >
Attachment
Watch this ticket