[Glass] Why session locking is necessary for Seaside?

Johan Brichau via Glass glass at lists.gemtalksystems.com
Tue Mar 21 16:00:20 PDT 2017

> On 21 Mar 2017, at 22:35, Kjell Godo via Glass <glass at lists.gemtalksystems.com> wrote:
> So what i think I'm hearing is
>      you can have gemstone gems
>      and Seaside gems
>      and the Seaside gems don't have the Reduced conflict Classes

No this is not what you should be hearing. 
This discussion is about serving requests for the same Seaside session concurrently.
A single Seaside session is about one user who is browsing your web app.

This has nothing to do with serving multiple sessions concurrently and processing requests for different sessions (and thus different users) in parallel.
Seaside can do that very well in GemStone, and using Rc classes inside your application will be very necessary for any shared state between the different sessions.

Hope this avoids confusion
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20170322/d1e2fdca/attachment.html>

More information about the Glass mailing list