On Mon 28 Apr 2008, woinshet abdella wrote:
> $r->add_config([
> 'PerlOutputFilterHandler BI::Apache::FilterBeforeIncludes',
> 'PerlSetOutputFilter INCLUDES',
> 'PerlOutputFilterHandler BI::Apache::FilterAfterIncludes']);
> =A0
> I want the response to be processed by the filters in the order specified
> in the configruation as shown above. However for SOME reqeusts, the second
> handler, FilterAfterIncludes, is initiated before the first one finishes.
> The second handler to work properly it should start just after the first
> one because it expects some shared variable that is set by the first
> handler. It appears that this happens when the size of the response is bi=

> is there any other way of forcing the order?

This is how filters work, no surprise. A filter is normally called multiple=
times per request. Each time it processes a chunk of the output as it goes=
down the output chain. When one filter has processed the chunk it is passed=
to the next filter until it is eventually sent out on the wire. Then the ne=
chunk does the same. So you cannot expect one filter to see the complete=20
output before another one is started.

You can of course do some tricks like catching the whole output in the firs=
filter throwing the buckets away. Then at end of stream you can reinsert th=
stuff. But that is quite complex. If you decide to go this way remember not=
to cache the stuff in RAM but to write it to file(s). Otherwise your=20
processes will waste a lot of memory.


Need professional mod_perl support?
Just hire me: torsten.foertsch@gmx.net