I think there needs to be a mod_fork which provides a more general purpose daemon than that used by mod_cgid, and some Apache API will know whether or not to send a request over there. This preserves the goal of having fork() called only by single-threaded processes so that all manner of pain is avoided.
Big +1 from me in concept.
I am not sure how to do the implementation best. mod_cgid doesn't really 'fork' in the sense most programs do, its mostly just starting up a cgi process -- from an executable on the file system.
This seems drastically different from the requirements of a generic fork().
Any thoughts on how you would want to implement this in a generic manner for any call from anywhere for any module?
-Paul Querna
