Derick Rethans wrote:
Hello,
after a little discussion on IRC, we came to the conclusion that it is not
a good idea to say that php 4.2.0 supports apache 2. The reasoning behind
is that we are not even 50% sure if apache 2(.0.35) works correctly, or
that the filter works correctly. This is because no single QA was done on
it and we wont be able to do that before the release. I do not want to
postpone the release because the apache dudes released their new workhorse
on a very short notice while rushing it to release. I am not confident
that apache 2 / PHP 4.2.0 is stable enough for production yet, and
therefore recommend to drop the apache2filter from the release branch. If
you can't do it properly, don't do it is my motto here. I hope this is
the same with you.
regards,
Derick
I'm -0.5 for this.
If we drop Apache2fileter support, there will be bug
reports/questions/complaints for this.
If we keep apahce2fileter support, there will be many
bug reports for it.
If I have to choose, I'll keep apache2 support and try
to let users know it's only good for experiment.
Let them fill bug reports so that we can fix for PHP4.3.0.
(I'll try to close bug reports, of course ;)
BTW, Apache2filter SAPI does not work well as Apache
SAPI for sure. But it's a lot faster for my usage.
--
Yasuo Ohgaki
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
