Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Date: Thu, 6 Feb 2003 09:59:27 -0800
Subject: Re: story posted
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v551)
From: Aaron Bannert <aaron@clove.org>
To: dev@httpd.apache.org
Content-Transfer-Encoding: 7bit
In-Reply-To: <3E413E52.7000902@wstoddard.com>
Message-Id: <BB85EAEF-39FC-11D7-B2CC-000393B3C494@clove.org>


On Wednesday, February 5, 2003, at 08:39  AM, Bill Stoddard wrote:
> Then reimplement PHP as a handler/generator. You get the benefits of 
> being able to install downstream filters w/o the headaches of 
> implementing a filter.  Personally I never thought implementing PHP as 
> a filter was a good idea to begin with. yea, it's more flexible but 
> that flexability comes at a high cost. And if no one is interested in 
> what that extra flexability gains you, then the only thing 
> accomplished is the code is more complex and bug prone. You know the 
> saying "if the only tool you have is a hammer, then all problems look 
> like nails"?  Well for a while, apache 2.0 filters were 'the hammer'.  
> Hopefully that is changing now.

I don't see how making it a handler will fix this problem.
PHP will still want to read input bodies from the input
filter chain.

Also, I should point out that something as seemingly simple
as an SSI file that includes multiple php scripts needs the
filter stack.

-aaron