The targeted architecture is : Apache2/mod_python/ZopeHandler <-> ZEO At startup Apache initialize a pool of child processes (the processes that handle requests). Each Apache child process starts a python interpreter (mod_python does it) which in turns initialize an embedded Zope instance. Child processes are reusable, so if you correclty set the pool in Apache, the python processes should live as long as Apache itself. Note that I am not an Apache/mod_python specialist. It's just that when I wanted to try running Zope with mod_python, I found on the web that apparently noone had done it before, and even that in odler versions of mod_python it was clearly stated that it was impossible to achieve. So I just decided to expose what I did to the community, to get feedback. My installation has now been running for 5 days, and I have still no issues, both browsing my site or using the ZMI. Pascal -----Message d'origine----- De : Chris Withers [mailto:chris@simplistix.co.uk] Envoyé : mardi 8 février 2005 11:36 À : Pascal Peregrina Cc : 'zope@zope.org ' Objet : Re: [Zope] RE: Zope and mod_python Pascal Peregrina wrote:
This is because each request is handled in a dedicated Apache process, which is linked to an independent python process.
Hmmm, how and where are connections made to the ZODB? Is there still a long-running process with this method? Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com **********************************************************************