Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Date: Wed, 5 Feb 2003 13:25:45 -0500 (EST)
From: Cliff Woolley <jwoolley@virginia.edu>
To: dev@httpd.apache.org, trawick@attglobal.net
Subject: Re: story posted
In-Reply-To: <3E413586.9020808@attglobal.net>
Message-ID: <Pine.LNX.4.52.0302051323430.12843@bistromath.cs.virginia.edu>
References: <Pine.LNX.4.44.0302050752070.1002-100000@thinkpad.lerdorf.com>
 <3E413586.9020808@attglobal.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 5 Feb 2003, Jeff Trawick wrote:

> What I think is useful information to people who want PHP+Apache-2.0 is:
>
> a) is PHP not production ready with Apache 2.0 because it was not high
> enough priority for PHP to be tested?
>
> b) is PHP not production ready with Apache 2.0 because Apache 2.0 must
> be fixed before such a thing is even possible?
>
> I see more comments implying b) than a).  As such, it seems that anybody
> that wants to hack PHP to work better with 2.0 is wasting their time.


Having looked at it in depth personally, I'll say a strong (a).  Aaron and
I had a good roadmap for how to get it all to work, and the only
modifications we needed to make were in Zend and PHP.  The current PHP
Apache2 filter assumes that it can get a file handle and other silliness.
But we never had the time to actually fix it The Right Way, and the other
PHP people seemed to just want to say "b! b! it's Apache's fault" so we
got into this finger-pointing standoff and nobody ever fixed anything.

--Cliff