On 4/13/05, Paul Querna <[EMAIL PROTECTED]> wrote: > Olaf van der Spek wrote: > > Hi, > > > > I originally posted this feature request to the bug tracker, but Joe > > Orton suggested it'd post it here instead, so here it is. > > > > I'd like to see a new 'MPM' that basically works like this: > > A single or few-threaded, non-blocking frontend that accepts incoming > > connections, receives requests and sends responses. > > A multi-threaded or multi-processed backend that processes requests, > > generates > > responses and passes the responses to the frontend for sending to the > > client. > > > > The advantage of this scheme would be that you can handle a (much) bigger > > number of clients/persistent connections with less resources. > > > > The event MPM is a step in the right direction, but not 'good' enough. > > > > A scenario with multiple backends may be possible to, for example one > > running as user A, one as user B, etc. > > Or one multi-threaded backend for static content and one > > multi-processed backend for dynamic content (PHP). > > > > http://issues.apache.org/bugzilla/show_bug.cgi?id=32243 > > > > I agree with just about everything you said, at least in concept. > > I am willing to help out, but I don't have the time or resources to head > up this type of project right now. If you do the initial work, I would > love to help get such an MPM into the mainline tree.
Wouldn't it be possible to start this 'transition' by writing a module that forwards the request to a separate backend process? That way, you could safely run the threaded MPM and still use PHP in a safe way.
