On Wed, 16 Jun 2004, Marc Richards wrote: > Going form Apache1 to Apache2, aside form filters (which you mentioned > in bug 27583) there is the default inclusion of mod_ssl and mod_ldap, > better Internationalization features, mod_perl 2.0 (which ONLY works > with Apache2), Subversion via WebDAV, and also the fact that many Linux > distribution ship Apache2+prefork by default (e.g. Red Hat Enterprise > Linux). Some of these features (mod_ldap and mod_perl) are still in the > experimental stages and therefore only run in development, but I want to > be able to standardize on Apache2 for development and production. To top > it off like you said Apache1 is pretty poor on Windows, so I also want > to standardize on Apache2 (without PHP) on windows and Linux.
You are right, the argument against Apache2+prefork is nowhere near as strong. What you list here has very little to do with PHP though, it has more to do with convergence of things onto a single platform for your particular needs. For me the motivation to put time into Apache2+prefork development is minimal. The module API has changed completely, so all my custom Apache modules will have to be rewritten and what do I get in return? Filters that I can't really use anyway? This is not compelling enough for me. There has to be a big win for me to take the migration hit. Just like if you tried to convince me to switch to aolserver or Caudium. It is a very different server and for the most part just shares the name. We felt the need for the warning to make sure people understood that Apache2 is not just the latest stable version of Apache1.3.x and that Apache1 is still the server we can with confidence say will work in a production environment. -Rasmus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
