As a stop gap, we've got the load balancer doing persistent binding based on SSL ID. The problem being of course that if one server goes down all the logged in users have to re-login. If the session were persistent across servers via ZEO then the user wouldn't notice the down event. -J On Fri, 11 Feb 2005 21:35:07 +0100, Tino Wildenhain <tino@wildenhain.de> wrote:
Am Freitag, den 11.02.2005, 19:55 +0100 schrieb Dieter Maurer:
Jason J. W. Williams wrote at 2005-2-10 12:51 -0700:
Is there more to it than updating the client with the ZEO Temporary section in the zope.conf?
I never tried your way (put sessions into ZEO).
We use a different scheme (code session key (including a host id) into the URL and use Apache rewrites to ensure any requests goes to the host where the session started.
Hehe. I remember reading many years ago about this technique is patented ;)