On Nov 4, 2008, at 12:15 PM, Paul Querna wrote:
Graham Leggett wrote:
Justin Erenkrantz wrote:
I think MPMs are a design mis-feature. The fact that the same
directive value can be (and is!) interpreted in non-uniform ways by
different MPMs bugs me to no end. -- justin
That is a flaw in the MPMs themselves (overloading a term is evil I
agree), but not in the MPM concept as a whole.
The fact we have MPMs at all gives us the power to develop
something like the simple MPM alongside existing stable MPMs,
without being forced to endure a period of instability where the
server doesn't work at all.
Its trunk, it better be unstable or we are doing something wrong.
Thats why I think we should delete prefork, worker, event,
threadpool, perchild, and leader MPMs.
Ummm... right now, trunk is the source for backports to
2.2.x.... Also, there are potential backports for these MPMs in
trunk that are not in 2.2.x.... So, if we decide, we either need
to branch off trunk to 2.2-dev and then delete, or branch off
trunk to httpd-nola and delete on *that* branch.
