[Seaside] Load balancing with one session per image
boris at deepcovelabs.com
Mon Jun 22 16:04:08 UTC 2009
The following is quite thin technical-detail wise, but might give you
some ideas nonetheless,
From: seaside-bounces at lists.squeakfoundation.org
[mailto:seaside-bounces at lists.squeakfoundation.org] On Behalf Of Bob
Sent: Monday, June 22, 2009 8:49 AM
To: seaside at lists.squeakfoundation.org
Subject: [Seaside] Load balancing with one session per image
How can we load balance across a number of VW Seaside images where we
each image to one Seaside session? So, once a Seaside session is
with a VW image, no other Seaside session can be serviced by that image.
The image is only available when the session expires or the user logs
For now we're using Apache and we're investigating Cherokee and Nginx.
Here's some background: we've added a Seaside interface to a current VW
application. The Seaside interface is designed as just another UI layer
the domain. There is enough meta data in the framework to drive a
thin Seaside layer which duplicates virtually all of the full (fat)
behaviour. But, because of framework restrictions, we'll only support
Seaside session per image. Since we're only looking at supporting
concurrent sessions, we don't feel the need to re-engineer the
framework code to support multiple session.
The Seaside components are built widget by widget from the VW windows
with callback behaviours triggering matching VW widget behaviours. We
prompts and window open events by using Process>>#environmentAt: to pass
Seaside session between the components and the domain.
So far, all of this is working fine. It is actually quite cool to show
full client side by side with a domain browser.
Thanks for any help,
View this message in context:
Sent from the Squeak - Seaside mailing list archive at Nabble.com.
seaside mailing list
seaside at lists.squeakfoundation.org
More information about the seaside