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

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7712
------------------------------------------------------------------------------
  Ticket             | 7712
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Memcache Session handler, shouldn't unlock if no data
                     | in memcache
  Queue              | Horde Framework Packages
  Version            | HEAD
  Type               | Bug
-State              | Assigned
+State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Slusarz
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2008-12-02 13:30) wrote:

> 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