Tres Seaver wrote:
This is the major benefit of the approach: sysadmins don't have to monitor / manage a separate daemon.
Well, you still need a seperate daemon for the storage server, but granted, that's one less than the usual setup of Apache - Zope Web - Zope Storage
Another potential benefit is that each child behaves as a single-threaded appserver, with no GIL-contention issues.
:-D
A potential downside is that the child processes will not be able to reused the local ZEO client cache.
Well, I assume they'll keep the same client cache for as long as the child process exists? I guess it would be nice to find a way that child process could use a persistent ZEO client cache, right? Does each child process need to have it's own client cache (I'm guessing the way Pascal currently has it working, that'll be the case, whether it's needed or not...) and if it doesn't, is there any way the processes could share the cache in the "mod_zope" setup? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk