That presents somewhat of a chicken-and-egg problem. Production sites won't be compelled to make a move until PHP recommends it in some way, or if there is a killer feature that pulls people in, regardless of the perceived stability.
Right, and they shouldn't. If there is no compelling reason to switch, why in the world should they? And why should we try to push them away from a stable platform?
Then perhaps some striking new functionality would push PHP 5/Apache 2. While Apache 2 introduces new complexities, using some of the new features could be advantageous, and a step towards the next generation. For instance, allowing PHP to reach deeper into Apache, to a level similar to that of mod_perl, could provide significant new features and value. Getting PHP to control URL rewriting and logging, for example, could be new features that drive demands from end-developers, and at the same time generates interest and challenges for those developing PHP and Apache themselves.
That has nothing to do with Apache2 and has been available for Apache1 for years. It just isn't a very popular feature. See the apache_hooks code.
-Rasmus
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
