Webware for Python

we use the webware sessions, yes.

the loadbalancer is administrated by the hosting company so I haven't 
got 100% knowledge of how that thing works... We configured it so 
that if the user is "placed" on server 2, he/she sticks to that one 
for the rest of the session...

Currently if we want to interact between several logged in users we 
do this through a separate "lobby" application placed on a separate 
server.


I guess as a future to do, we'll try to fix so it would be possible 
to share some custom netbaby player sessions between the servers.



At 11:19 -0400 02-09-26, Geoffrey Talvola wrote:
>Great writeup -- thanks!
>
>I do have one question.  Do you use Webware's sessions?  If so, how do you
>handle load balancing so that requests for the same session go to the same
>box?
>
>- Geoff

> I guess as a future to do, we'll try to fix so it would be possible to 
> share some custom netbaby player sessions between the servers.

If you centralize the session info (like in a database) then you add 
overhead to each page. Most load balancing sticks on a certain machine 
so the session system can use a memory store.

Of course the downside w/ this is that is a server dies all of its users 
will have to start over.

Central sessions = availability
Machine affininty = speed

Personally I think the main challenge is to provide a means for webware 
to feeback some type of load information to the load balancer, so that 
there can be some intelligent balancing.  There are some python limits 
that may be below the hardware limits (Single vs Dual proc) as well as 
some application resources that you may hit.

A apache type Server-Status would be a nice addition to Webware.

-Aaron

Aaron Held wrote:
> Personally I think the main challenge is to provide a means 
> for webware 
> to feeback some type of load information to the load 
> balancer, so that 
> there can be some intelligent balancing.

If the load balancer is capable of examining the cookies, it could balance
based on the value of the _SID_ cookie.

- Geoff