perl-modperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Solutio at Gmail" <solu...@gmail.com>
Subject Re: Capturing Apache response
Date Fri, 13 Feb 2009 19:42:04 GMT
We'll look at pnotes too. Thanks again.

--------------------------------------------------
From: "Mark Hedges" <hedges@scriptdolphin.org>
Sent: Friday, February 13, 2009 1:11 PM
To: "Solutio at Gmail" <solutio@gmail.com>
Cc: "André Warnier" <aw@ice-sa.com>; <modperl@perl.apache.org>
Subject: Re: Capturing Apache response

>
> I'm trying to say that you shouldn't use custom headers to
> save this information, when you should be using the correct
> facility, which is pnotes.  Why do you want to use the wrong
> thing when the right thing is available?
>
> Mark
>
> On Fri, 13 Feb 2009, Solutio at Gmail wrote:
>
>> I understand your point, and we'll strip the custom headers off before 
>> sending
>> the response to the client. We are also looking at another way to dump 
>> the
>> response (in the application's parent template class), which would help 
>> us
>> avoid messing with Apache altogether.
>>
>> --------------------------------------------------
>> From: "Mark Hedges" <hedges@scriptdolphin.org>
>> Sent: Friday, February 13, 2009 12:07 PM
>> To: "Solutio at Gmail" <solutio@gmail.com>
>> Cc: "André Warnier" <aw@ice-sa.com>; <modperl@perl.apache.org>
>> Subject: Re: Capturing Apache response
>>
>> >
>> >
>> >
>> > On Tue, 10 Feb 2009, Solutio at Gmail wrote:
>> >
>> > > First of all, I thank you both for your expert opinion on the topic. 
>> > > I
>> > > have
>> > > never had to fiddle with this sort of Apache customization, so I'm
>> > > learning in
>> > > the process...
>> > >
>> > > As for the way to communicate the file name to the filter, sure, we 
>> > > would
>> > > like
>> > > to keep it as simple as possible and avoid pitfalls. I agree that 
>> > > Perl is
>> > > a
>> > > powerful tool that can easily screw many things up if applied 
>> > > carelessly.
>> > >
>> > > I guess if we properly implement the custom header option, it 
>> > > shouldn't
>> > > become
>> > > a problem. We'll give it a try.
>> >
>> > To recap, you shouldn't use the custom header, you should
>> > probably use $r->pnotes or maybe $c->pnotes to store the
>> > information from the beginning to be accessed at the end.
>> > This is what the pnotes tables are for.  Don't mess with the
>> > headers.  Headers are for communicating with the client.
>> >
>> > Mark
>> >
>> 

Mime
View raw message