*cackle* Ok, and after I get fired for having to explain to my boss that it was my fault that the server was down because I was playing with experimental code, I'll have plenty of time to write you back about the problems I encountered :)
Seriously though, if at this point, all the 'base code' of PHP is certified, could it be possible to start a checklist of which modules have been certified and which haven't? In the code we will be using, we are actually using surprisingly few libraries: Arrays, Date/Time, Directories, Filesystem, and Math ... If a list could be formed, of what was definitely safe, then perhaps some people, like us, could start using it earlier, knowing that we weren't doing other stuff (like image manipulation, DB access, etc.) Eli >The best way for PHP's Apache 2.0 module to escape from "experimental" >status is to have the confidence of sites like yours running the >code. Most of the showstopping bugs have been fixed. You can see a list >of the outstanding bugs on our bug tracking site: http://bugs.php.net/ > >I suggest you take PHP 4.2.1 with Apache 2.0.36 (running the worker >MPM) and run your workload on it. At this point the only uncertainty >with the code comes from the multithreaded nature of Apache 2 and how >that will interact with 3rd party libraries that may not be reentrant >or threadsafe (as Rasmus points out). > >If you encounter any bugs, please report them. More importantly, if >you have success please let us know. :) > >-aaron (one of the apache2filter maintainers) -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
