Paul Querna wrote:
I was hoping someone will address the separation of
child process management from the mpm.
Majority of this stuff is common and duplicated across
mpms while there can be an api for that thought.
Yes, the simple mpm inteded to go there, and only uses APR functions
for threadpools/fork/processes, rather than native OS functions like
the existing winnt/worker/prefork MPMs.
Well the problem is that apr isn't enough there.
Bill proposed to add registry (not sure about SCM)
code to the apr, but was rejected. There is
also a problem of sending the sockets to the child.
So one would still need the 'os' layer hooks where
os part of the mpm can do it's work.
Although good, the simple mpm isn't much of the
use solving that.
Like said earlier. You guys should start thinking
like a Windows developer :)
Regards
--
^(TM)
