On Mon, Nov 22, 2004 at 07:29:51AM +1100, skaller wrote:
> However consider also a second problem with mod_caml: unloading.
> That's also essential for a long running process, and can't be done,
> even in the bytecode interpreter. There were *also* patches
> made for that (mods to the garbage collector to allow code
> to be collected).

This isn't actually much of a problem with mod_caml.  Deployments of
Apache should limit the number of HTTP requests that a single Apache
child can handle (MaxRequestsPerChild), after which the child exits.
This parameter is commonly set low with mod_perl also, since Perl has
several "issues" with running over long periods of time - it was
designed for short command line scripts after all.

Rich.

-- 
Richard Jones.  http://www.annexia.org/  http://www.j-london.com/
>>>   http://www.team-notepad.com/ - collaboration tools for teams   <<<
Merjis Ltd. http://www.merjis.com/ - improving website return on investment
http://winwinsales.co.uk/ - CRM consultancy