[Glass] System>>#writeLockAll: and Seaside

[Dale Henrichs via Glass]

Paul,

Are you talking about the writeLock acquired on the session in 
WAGsMutualExclusionFilter>>handleFiltered:?

If so, the lock is acquired such that the lock is removed once a commit 
or abort occurs ... or if the session crashes ...

These locks are held on the session object while the gem processes an 
http request and are used to prevent multiple gems from processing 
requests for the same session concurrently ... the lock is reliquished 
when the gem commits or aborts (or crashes) thus allowing another gem to 
process rquests on behalf of the session, so in this case the Seaside 
session is "respecting the Seaside session"....

Perhaps you are looking at a different use case involving session 
affinity or something?

Dale

On 04/27/2016 10:20 AM, PAUL DEBRUICKER via Glass wrote:
> Hi -
>
> It is my understanding that the read/write locks are held by the gem session.   Seaside sessions can move around among gems and also outlive gems, in the event of a gem crash.
>
>
> Is there a recommended way to lock objects and have them respect the Seaside session, rather than the Gem session and if not how are others doing locking with Seaside?
>
>
> Thanks
>
> Paul
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/glass