I once worked with a perl system that spawned many, many daemons from a
large perl code base. It had an elaborate system of several steps of
forking and restarts of child processes with eval'd 'use' statements so
that each daemon only compiled, and was running, its own minimal amount
of code, rather than the full set of code. Looked like an entirely
custom-made system. Are there other (hopefully simpler and more
direct) schemes to achieve this result?
Probably not as critical an issue these days as it was when that system
was created in the early 2000's, but still interesting in some situations.
Thanks,
Jim Eshelman
_______________________________________________
Boston-pm mailing list
[email protected]
http://mail.pm.org/mailman/listinfo/boston-pm
