Hi,

Sorry to jump in here...
[vbcol=seagreen] 

Quite. It means the existence of a session means it is locked.

If a lock exists for the duration of a session rather than the duration
of a request, how do you differentiate the user opening the page in
another tab/window and then attempting to navigate/interact on both of
them? This would therefore make the concept of the session lock
redundant (from what I understand above). Therefore the only thing you
can protect against is concurrent access to the storage - its one of the
downsides of server-side sessions.

Im sure ive missed something about this...a few pointers to where my
thinking is going wrong would be appreciated.

Cheers,
Barry

[ Post a follow-up to this message ]