Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (nike.apache.org: domain of solutio@gmail.com designates
 209.85.217.175 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:from:to:cc:references:in-reply-to:subject:date
         :mime-version:content-type:content-transfer-encoding:x-priority
         :x-msmail-priority:importance:x-mailer:x-mimeole;
        b=K4+i7p7npUfEyR4TRmHHkHVw8z+64GxjeTBRsRHLpoCLyJNt1IX3So+t9PROFsXjBy
         eeU5SwgtDj0vXLjisMTLkSlkRc+iyC043AexfoixOuOeZU1N25XmOjhFDSveEUP3I9ID
         99zNigO5VpT78XAmEdQ4oha1fUjQHPPMmY8eM=
Message-ID: <F4A7773C51FC4C8AA29956DDCC6D3388@ICAD820ASAIP>
From: "Solutio at Gmail" <solutio@gmail.com>
To: "Mark Hedges" <hedges@scriptdolphin.org>
Cc: =?iso-8859-1?Q?Andr=E9_Warnier?= <aw@ice-sa.com>,
	<modperl@perl.apache.org>
References: <B6EC6E204A324A0B88AC76BBC721EFD1@ICAD820ASAIP>
  <498F6A36.1050308@ice-sa.com>
  <B6EFBD7F1E564FDFA3E8AC4EFA183B3B@ICAD820ASAIP>
  <498F87BE.9070900@ice-sa.com>
 <b117dd460902092152g5625612hc6c5d5832329ccb5@mail.gmail.com>
 <alpine.DEB.1.10.0902101228340.26806@li16-163.members.linode.com>
 <4991F9DC.7020002@ice-sa.com> <173B8D1674A746ADAF9F3EEE5D383A4E@ICAD820ASAIP>
 <alpine.DEB.1.10.0902131005330.12818@li16-163.members.linode.com>
 <2AC81BE16DF1468B871903C46D4E8DA8@ICAD820ASAIP>
 <alpine.DEB.1.10.0902131110380.12818@li16-163.members.linode.com>
In-Reply-To: <alpine.DEB.1.10.0902131110380.12818@li16-163.members.linode.com>
Subject: Re: Capturing Apache response
Date: Fri, 13 Feb 2009 13:42:04 -0600
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 8bit
Importance: Normal

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
>> >
>>