[Seaside] apache + seaside

Avi Bryant avi.bryant at gmail.com
Fri Nov 25 22:14:48 CET 2005

On Nov 25, 2005, at 1:04 PM, David Shaffer wrote:
> I almost always use 1 since I like to be able to hit the seaside  
> server
> without having to go through the proxy.  In practice I have a separate
> space for seaside apps so the "/seaside" path works just fine for me.
> It's just a matter of proxying to the right port # (and from SSL to
> non-SSL).  I use this to switch between two production images as well.
> There is an article floating around on using rewrites to load balance
> with session affinity...I use this basic technique to switch between
> production images (not for load balancing, just to move new  
> sessions to
> a newer version of my software).  If you really want more flexibility
> with URL mappings then you're probably going to have to struggle a bit
> to get there.  Keep us posted ;-)

I've been using Pound (http://www.apsis.ch/pound/) lately for load  
balancing and switching between images.  It doesn't do any URL  
rewriting at all (just proxies through to an internal port), but is  
fairly flexible about matching on URLs or headers (so you can rig up  
a vhost setup if you want, for example).  The nicest feature is that  
it tracks the status of the backend servers and fallback to a  
secondary server if the primary goes down.  I use that to lazily  
bring up images on demand - the fallback server just starts them up  
and passes on the request.

The least nice feature is that is has no way to change the  
configuration without an ungraceful restart, which drops any active  
connections.  It also seems to have some stability issues if you have  
keepalive turned on in the backend (so you need to disable that on  

I'd love an equivalent of its fallback feature on apache, but haven't  
found it so far, and haven't felt inspired yet to write a custom module.


More information about the Seaside mailing list