20 Nov
2003
20 Nov
'03
7:42 p.m.
On Thu, Nov 20, 2003 at 07:07:46PM +0000, Lee J. McAllister wrote:
My assumption is that, being a threaded process, it spawns a child to handle any requests/subprocesses so that it isn't blocked from receiving new requests while current ones are being handled.
The process forks to form a daemon process and the actual Zope server; the daemon process then can restart the Zope serevr at will (in case it dies or is restarted explicitly). The Zope server itself doesn't fork to deal with requests; it handles those with a pre-allocated thread pool. -- Martijn Pieters | Software Engineer mailto:mj@zope.com | Zope Corporation http://www.zope.com/ | Creators of Zope http://www.zope.org/ ---------------------------------------------