[Glass] System>>#writeLockAll: and Seaside

[PAUL DEBRUICKER via Glass]

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