Aaron Bannert wrote:
So is that a popular configuration in use with 1.3 today? If not, then I hold this up as a trophy illustrating my earlier assertion regarding overengineered 'solutions' to non existent problems.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
Bill
