I don't see any chance that Apache2+PHP is production quality in a month.
There are simply too many new things for that to be the case. A bunch of
the 3rd-party libraries you can link into PHP may or may not be completely
threadsafe. We simply don't know yet. The Apache2 module itself has had
virtually no testing, so issues in that are unknown as well.
6 months is much more realistic as far as I am concerned.
On Mon, 13 May 2002, Eli White wrote:
> As the subject says, can anyone give me a timeline estimate for full
> usage (not experimental) of PHP within Apache 2.0?
> I ask because I am the maintainer of a server that recently got LOADS of
> hits, and was brought to it's knees (Hubble Space Telescope). We
> managed through, but during problem solving afterwards we have decided
> that Apache 2.0 with it's threads would have helped us greatly under our
> the problem is that we were just getting ready (in say a month) to go
> live with a very large PHP piece ... and if they can't work together ...
> well ... hrmmmm.
> Computer Specialist for Internet Services
> [EMAIL PROTECTED]
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php