I know that Apache 2 discussions have come up before, so I will make my question very specific. Given that pre-fork is the default Apache mpm on linux systems, why doesn't PHP have non-experimental support for Apache 2 when using this module?
I realize that there are thread-saftey issues when using the worker mpm, but I fail to understand why experimental status is not restricted to non pre-fork modules, especially considering that pre-fork is default configuration for the official apache binaries and on most linux distros. I also realize that not everybody will be immediately convinced by the virtues of apache 2, but there are still very ligitimate reasons for using it. For example, there are newer modules (like Subversion) that require Apache 2.0, there are new features like filtering and IPv6, and also now that Apache 2 has better support on Windows it is easier to standardize on Apache 2 accross OSs even if you only install php on you linux boxes. The imporoved documentation and config directives alone are reason enough for me to upgrade. I understand that PHP development is driven by volunteers who don't have unlimited time to develop features that do not interest them, and I understand that there were a lot of compatibility problems with Apache in the beginning, but it seems like at this point it is just being marked as experimental out of spite. Isn't Apache 2 fairly similar (in terms of stability) to 1.3 when using the prefork mpm? What would it take at this point to get it declared stable? Is there a problem with the code or is it just fear of the unkown and untested? Is this the responsiblility of the PHP QA team? Can users help out with testing? Redhat apparently feels confident enough to include Apache 2 (and PHP4) in their upcoming Redhat Enterprise 3 product (http://ftp.redhat.com/pub/redhat/linux/beta/taroon/en/as/i386/RELEASE-NOTES -en), so I assume that at least they have tested it. I often feel like there are features (Apache2 support, Application level vars, Built in DB abstraction) that many users want and that come up over and over but just get dismissed because the don't necessarily appeal to the current developers, even though they might be beneficial to the community at large. I am in now way blaming the developers for this, it comes with the territory of the current development model. It would be nice however if there was an wat users who aren't C coders to make there collective voices heard with regards to features, and maybe then a company like Zend could sponsor a developer to work on those features. Marc P.S. This wasn't just a stress reliving rant, I am actually interested in answers to my question. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
