Personally, I completely understand that is all new code and bugs will occur. I won't be going to Apache 2 for some time to come. The only reason I even tried it at all is I already was already getting requests on php-tuxedo for that combo so I thought I should give it a try.
But I hope the Bugus link works well on the bug mailing list cuz you will probably be getting quite a few. And from the public perception it just looks bad. And that is my main point. It just looks bad. As for Apache being at fault too, they very well could be. But the fact remains that PHP runs INSIDE Apache, and Apache starts fine without PHP, hence PHP must be at fault. Simply stating the obvious facts from the public point of view. Brian On Mon, 22 Apr 2002, Rasmus Lerdorf wrote: > > That is exactly my point. I no more than read the encouraging report that > > its been identified and is close to a fix, and the next message says > > 4.2 has been released. > > > > It couldn't have waited just another week to get this fix in and tested? > > No, because it wouldn't make much of a difference. There will be other > bugs. This is brand new code. Like I said, it will take a couple of > months to stabilize. People should not be running Apache2+PHP in > production yet. > > Any why exactly are you focusing on PHP here? Why not complain to the > Apache folks about releasing Apache 2 before this was cleared up? This is > not likely to be a PHP-specific bug and will require changes on both > sides. > > -Rasmus > > > -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
