Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: domain of adam.prime@utoronto.ca
 designates 128.100.132.151 as permitted sender)
Message-ID: <4B9C53E9.3090108@utoronto.ca>
Date: Sat, 13 Mar 2010 22:11:37 -0500
From: Adam Prime <adam.prime@utoronto.ca>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Iain Kennedy <iain@psand.net>
CC: modperl@perl.apache.org
Subject: Re: Upgrading chained response handlers to mod_perl2
References: <4B98BE2F.7040406@psand.net> <4B9C2045.2080801@psand.net>
In-Reply-To: <4B9C2045.2080801@psand.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Iain Kennedy wrote:
> Hi,
> 
> Is there a data structure that gets passed to each response handler in
> the chain that the processed file can be stored in (like $f->ctx)?
> 
> Can the old mod_perl1 ->filter_input behaviour be done by manipulating
> the input_filter or output_filter stacks?
> 
> Is what I'm trying to do vaguely sane, even? With the following directive:
> 
> PerlResponseHandler +Module::Test1 +Module::Test2

I'm not sure, but i don't think you can really do that in mp2, i think 
you need to read about how filters work in mp2, then do something like

PerlResponseHandler Module::Test1
PerlOutputFilter Module::Test2

where Module::Test2 has been rewritten using the filter API.  Geoff 
Young gave a talk about filters at an apachecon many moons ago that i 
found particularly helpful, you can still find the slides here:

http://www.modperlcookbook.org/~geoff/slides/ApacheCon/2006/mp2_filters-printable.pdf.gz


> Having both Test1 and Test2 process the HTML response body in turn with
> mod_perl1 was pretty straightforward. I reckon I must be missing
> something pretty obvious, surely?
> 
> Iain

HTH,

Adam