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 [..snip..]
Sort of, Kind of, in some ways, yes. In other ways, it is not anything like a 'complete rewrite'.
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)
Sounds logical to me.
[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]
Am I missing something?
http://httpd.apache.org/docs-2.0/mod/mod_proxy.html#proxypreservehost
I haven't seen any specific complaints out of this entire conversation, just a general feeling that it isn't tested as much. As one of the Apache Developers, I would be happy to help with any issues PHP has in its Apache 2 SAPI.
-Paul
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
