On Monday 03 September 2001 15:42, Rasmus Lerdorf wrote:
> > Multiple filters in the chain for each classification can exist
> > (ordering between classifications shouldn't matter...) This
> > way you can have a URL handled by mod_include and mod_php (but
> > the mod_include portion can't create PHP tags and vice versa
> > since you can't guarantee when it will run in relation to the
> > other).
> >
> > I have no clue how this relates to our code or how others sees
> > this. This is my quick uninformed birds-eye view. Thoughts?
> > This ordering seems to be a problem that we need to address.
>
> Definitely. One of the most requested features in the past has been
> stacked content handlers, and if we now say that we support stacked
> modules as long as they aren't content handlers, then a lot of people will
> wonder what the heck we are doing.
>
> There should be a way to specify ordering of the content handlers in the
> stack.
There is. In fact, there are TWO ways to configure this. The first way, is
to do it in the config file. If you do:
AddOutputFilter INCLUDES PHP
Then mod_include will always be run before mod_php. the second way is
for module authors to do this. Each module has an insert_filters phase. By
ordering the insert_filters phase, you can order which filter is called when.
If for some reason, the PHP developers always wanted to run before mod_include,
then they should specify that the php insert_filters phase runs before the
mod_include insert_filters phase.
Ryan
______________________________________________________________
Ryan Bloom [EMAIL PROTECTED]
Covalent Technologies [EMAIL PROTECTED]
--------------------------------------------------------------
