On Tue, 21 Dec 2004 00:19:50 +0100 (CET), in php.internals [EMAIL PROTECTED] (Derick Rethans) wrote:
>Why would we (as PHP developers) invest time in something while the >current version provides us with all we need? To sum the current webpages up (under the unix-install-page): "Installation under Apache1? Okay, note that.." "Installation under fhttpd? Okay, note that.." "Installation under Caudium? Okay, note that.." "Installation under Sun Java System Web Server? Okay, note that.." "Installation under Sun ONE Web Server? Okay, note that.." "Installation under iPlanet? Okay, note that.." "Installation under Netscape server? Okay, note that.." .. but "Installation under Apache2? NOT IN PRODUCTION!" I suppose the question is rather why we ask people not to use Apache 2.0.x and PHP in a production environment (as mentioned at http://www.php.net/manual/en/install.unix.apache2.php ), instead of just recommending using Apache2-prefork, if people really want to use Apache2. After all, the page with the warning is about is how a Apache2-user installs PHP, not "What webserver do you recommend". If that really was the case, why don't we have the same disclaimer at the fhttpd-page, the Caudium-page and the Sun, iPlanet and Netscape-page (all mentioned at http://www.php.net/manual/en/install.unix.php )? I haven't Netcrafted for the numbers, but I reckon there are more Apache2-prefork with PHP out there in production than Caudium-servers running PHP. If this is the case, how can we discourage people from running one specific webserver, but not all the other webservers? As the FAQ mentions, Apache2 is a complete rewrite and might as such be considered as a whole different webserver than Apache, just as Caudium, fhttpd, et cetera. I don't think it makes any sense to discourage Apache2 just because the reason is that the developers have more experience with Apache1. Just think of Apache2 as "Yet another webserver" (where the installation-notes would just mention that it has to run in prefork-mode) [a bit offtopic: I really miss the ProxyPreserveHost directive in Apache1, but I suppose that I and other developers just use some /etc/hosts-workaround if multiple domains has to be proxypassed to the same internal webserver. Not all administrators are able to perform these kind of stunts, though, so I guess that this just doesn't seem as much of a problem for those people with full root access to the entire system] -- - Peter Brodersen -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
