On Tue, Mar 24, 2009 at 12:41 PM, Mladen Turk <[email protected]> wrote:
> Jeff Trawick wrote: > >> >> (no plans here to touch WinNT MPMs, and I don't see any compelling reason >> to leave it broken; it should build as before once the inevitable minor >> slips are corrected) >> >> > The major problem with that is the huge amount of platform > dependent code for managing the service, registry and fork. > (Although -k install and -k uninstall could be a separate > utility app) Maybe its the lack of sleep, but I see that as a separate code reuse issue. I'm not trying to address code reuse with this effort, except with minor details where the solution to cutting the ties to the MPM involves a shared definition. > You could probably consider adding extra hooks that won't > do anything on *nix but would allow to easily plug the > NT mpm in this new layout. > If you go from the WinNT requirements, the *nix would fit > easily in this schema with just few no-ops for launching the > child process and sending the sockets, etc... > Help me understand why this isn't orthogonal to cutting the hard-coded tie to the built-inMPM ;)
