-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dieter Maurer wrote: >> ... >> You have that point-of-failure anyway if you are using the RAM-based >> sessions provided by Zope's core sessioning. If availability is >> important to you, then you *need* to be using ZEO and a load balancer, >> at which point you also have to look at a more scalable / available >> sessioning solution. > > We are using ZEO, a load balancer and nevertheless have sessions in RAM. > > True, it is less safe than with persistent sessions -- but it > is also more efficient. > > We do this by ensuring that independent of the load balancer's choice > a request for a given session goes to that Zope instance that has this > session.
Then you have the problem the orignal poster was trying to avoid: you can't restart an appserver without losing session data for some users. Externalizing the session storage removes the appserver as a point-of-failure for user sessions. Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v188.8.131.52 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFE2iTZ+gerLs4ltQ4RAn3HAKDNYodL3ENdV/jrQZhmEEtMkIQnbwCfbT+5 xH3krOiXo7KRd5G+DiEp92I= =WLfz -----END PGP SIGNATURE----- _______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )