[Seaside] Load balancing with one session per image

Bob Nemec bobn at rogers.com
Mon Jun 22 16:54:38 UTC 2009


Boris, 
Thanks, that's one of the threads I read.  I can see how it would be useful
as a way to manage the pool of images, but not in how it could isolate one
session per image.  Requests get proxied to the image's dedicated internal
port if it the port is open.  What I'd like is some way of indicating that
the port is not available, even though it's open. 

FWIW: we're thinking of keeping a fixed number of images up and have a hard
limit to the number of concurrent sessions.  Given the stats from how the
full client is used, we don't think that will be a problem.

Bob


Boris Popov-2 wrote:
> 
> The following is quite thin technical-detail wise, but might give you
> some ideas nonetheless,
> 
> http://tinyurl.com/n8uktc
> 
> -Boris
> 
> -----Original Message-----
> From: seaside-bounces at lists.squeakfoundation.org
> [mailto:seaside-bounces at lists.squeakfoundation.org] On Behalf Of Bob
> Nemec
> 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
> limit
> each image to one Seaside session?  So, once a Seaside session is
> affiliated
> 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
> out.
> 
> 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
> to
> the domain.  There is enough meta data in the framework to drive a
> fairly
> thin Seaside layer which duplicates virtually all of the full (fat)
> client
> behaviour.  But, because of framework restrictions, we'll only support
> one
> Seaside session per image.  Since we're only looking at supporting
> around 50
> concurrent sessions, we don't feel the need to re-engineer the
> application
> framework code to support multiple session.
> 
> The Seaside components are built widget by widget from the VW windows
> spec,
> with callback behaviours triggering matching VW widget behaviours.  We
> trap
> prompts and window open events by using Process>>#environmentAt: to pass
> our
> Seaside session between the components and the domain.
> 
> So far, all of this is working fine.  It is actually quite cool to show
> the
> full client side by side with a domain browser. 
> 
> Thanks for any help,
> 
> Bob Nemec
> Cherniak Software
> -- 
> View this message in context:
> http://www.nabble.com/Load-balancing-with-one-session-per-image-tp241498
> 15p24149815.html
> Sent from the Squeak - Seaside mailing list archive at Nabble.com.
> 
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> 
> 

-- 
View this message in context: http://www.nabble.com/Load-balancing-with-one-session-per-image-tp24149815p24151291.html
Sent from the Squeak - Seaside mailing list archive at Nabble.com.



More information about the seaside mailing list