"output filter" should always run /after/ any modules which
generate content.
So, it is probably difficult to have a filter which runs /in-between/
other Apache modules.
I'm still going to have a look at mod_perl filters - I have a feeling
they could be useful here and there.
Thanks :)
Tim
--
Tim Watts
Personal Blog: http://www.dionic.net/tim/
On 14/07/11 14:38, André Warnier wrote:
Tim Watts wrote:
...
"I think for this problem, I have to treat tomcat as a little, rather
inefficient, black box .."
They liked that quote then? ;->>>>
I'm sure it's a lovely development environment (there mu
ption.
And it is certainly a good tool to have in one's toolcase.
I agree - I'll have a look at that after I play with Alex's suggestion
of Varnish :)
Thanks very much for your time :)
all the best,
Tim
--
Tim Watts
Personal Blog: http://www.dionic.net/tim/
probably doomed to grief.
Thanks for the tip - I'm off to try that today!
All the best,
Tim
--
Tim Watts
Personal Blog: http://www.dionic.net/tim/
cat as a little, rather
inefficient, black box and try to fixup on the apache front ends, hence
the direction of my original idea...
Cheers,
Tim
--
Tim Watts
Personal Blog: http://www.dionic.net/tim/
er on Apache 2.2 *between*
mod_proxy and mod_cache?
Or am I going to have to implement a filter that includes proxying
and/or caching?
Many thanks for any advice,
Cheers,
Tim
--
Tim Watts
Personal Blog: http://www.dionic.net/tim/
