On Nov 2, 2008, at 1:04 PM, Justin Erenkrantz wrote:
On Thu, Oct 30, 2008 at 6:06 AM, Jim Jagielski <[EMAIL PROTECTED]>
wrote:
I tend to agree... as long as the architectural design doesn't
prevent people from creating (or keeping) MPMs, then this is all
good. Believe it or not, as people on the front-lines of handling
Apache setup and support for organizations can attest to, MPMs are a
valued feature.
I disagree. It's incredibly confusing to have compile-time
definitions and inability to adjust them at run-time.
I'd prefer that we remove all MPMs and teach whatever remains to be
able to emulate prefork (multiple-process/single-thread) or worker
(multiple-process/multiple-thread) at run-time.
You miss my point. If we just have one MPM, and make it
such that other MPMs are at a significant advantage, then
why even have MPMs? Hardcode in simple and be done.
In any case, we can pretty much do that with Worker now,
as well as Simple...
