[Glass] Workaround to browser maximum connection limit ?

Johan Brichau via Glass glass at lists.gemtalksystems.com
Mon Mar 20 23:20:23 PDT 2017

Hey Mariano,

> On 21 Mar 2017, at 01:01, Mariano Martinez Peck via Glass <glass at lists.gemtalksystems.com> wrote:
> The second thing is that making this on AJAX calls, that would end up on different Gems on my GemStone which was very performant. I have 10 Seaside gems on a 8 cores CPU so all those AJAX request were load balanced via nginx over the 10 seaside gems, which on the other hand were split across all cores. Previously, with a single request, only one Gem took care and hence only one CPU core was used. 

Quick question: does this mean these requests are "Seaside session-less”?
Because processing seaside requests in parallel is not possible (the session object is locked).

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20170321/dcd4df78/attachment.html>

More information about the Glass mailing list