FWIW, the session data problem can be solved with the use of a ZODB
session data container that is not stored in RAM (e.g. an SDC that is
not /temp_folder/session_data), or a reimplentation of a session manager
that uses a relational database or the filesystem.
The proxy error issue should be solved by using multiple Zope servers
and a load balancer which allows you to remove each from the service
pool before restarting it.
On Tue, 2006-08-08 at 12:24 +0200, Lennart Regebro wrote:
> On 8/8/06, James Davies <[EMAIL PROTECTED]> wrote:
> > People pay large sums of money for us to host there critical business
> > infrastructure. If we have to restart zope for any reason, people get apache
> > proxy errors and lose session data.
> Well, right the session data would be annoying.
> But still, most companies do accept that you schedule upgrades, and I
> still would like to know what kind of business can't accept a
> one-minute scheduled outage from time to time. I sure never have met
Zope maillist - Zope@zope.org
** No cross posts or HTML encoding! **
(Related lists -