[Seaside-dev] supporting vm routes

[Ramon Leon]

> 
> Setting up a cluster with four images could look something like this:
> 
> <Proxy balancer://mycluster>
> 	Order deny,allow
> 	Allow from all
> 
> 	BalancerMember http://127.0.0.1:8080/ loadfactor=1 
> route=33 min=1
> max=50 keepalive=On
> 	BalancerMember http://127.0.0.1:8080/ loadfactor=1 
> route=34 min=1
> max=50 keepalive=On
> 	BalancerMember http://127.0.0.1:8080/ loadfactor=1 
> route=35 min=1
> max=50 keepalive=On
> 	BalancerMember http://127.0.0.1:8080/ loadfactor=1 
> route=36 min=1
> max=50 keepalive=On
> 
> </Proxy>
> ProxyPreserveHost On
> ProxyPass /seaside balancer://mycluster/seaside STICKYSESSION=_s|_s
> nofailover=On
> ProxyPassReverse /seaside balancer://mycluster/seaside
> 
> To support this in Seaside we need to change the session key
> generation. We need to be able to append a suffix that is configured
> in the application. Julian you've spent a lot of time on sessions and
> cache and stuff. What do you think is the best way to implement this?
> A WAClusteredApplication that has a WARouteCache?
> 
> How do other people feel about this? Is this useful? Should this be
> part of Seaside out of the box or rather be an addon like
> Seaside-Cluster?

I used to do that but frankly ProxyBalancer sucks; it makes rolling out new
code very hard because you can't just dynamically fire up a bunch of new
servers and shift the traffic.  

Load balancing with just RewriteRules works much better and allows you to
dynamically shift traffic to new code while keeping the old code up until
those sessions die off.  Ask Lukas, he'll say the same thing.

Ramon Leon
http://onsmalltalk.com