Mailing List Archive

Re: cvs commit: modperl-docs/src/docs/2.0/user/config config.pod
geoff@apache.org wrote:
> geoff 2004/01/30 11:34:31
>
> Modified: src/docs/2.0/user/config config.pod
> Log:
> added some subprocess_env details
>
> Revision Changes Path
> 1.58 +9 -3 modperl-docs/src/docs/2.0/user/config/config.pod
>
> Index: config.pod
[...]
> +=item *
> +
> +Entries added to C<%ENV> are passed on to the C<subprocess_env> table,
> +and are thus accessible via C<r-E<gt>subprocess_env> during the later
> +C<PerlLogHandler> and C<PerlCleanupHandler> phases.

and in sub-requests?

__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
Re: cvs commit: modperl-docs/src/docs/2.0/user/config config.pod [ In reply to ]
Stas Bekman wrote:
> geoff@apache.org wrote:
>
>> geoff 2004/01/30 11:34:31
>>
>> Modified: src/docs/2.0/user/config config.pod
>> Log:
>> added some subprocess_env details
>> Revision Changes Path
>> 1.58 +9 -3 modperl-docs/src/docs/2.0/user/config/config.pod
>> Index: config.pod
>
> [...]
>
>> +=item *
>> +
>> +Entries added to C<%ENV> are passed on to the C<subprocess_env> table,
>> +and are thus accessible via C<r-E<gt>subprocess_env> during the later
>> +C<PerlLogHandler> and C<PerlCleanupHandler> phases.
>
>
> and in sub-requests?

and in response level filters! won't mod_include see these %ENV changes?

__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
Re: cvs commit: modperl-docs/src/docs/2.0/user/config config.pod [ In reply to ]
>> +Entries added to C<%ENV> are passed on to the C<subprocess_env> table,
>> +and are thus accessible via C<r-E<gt>subprocess_env> during the later
>> +C<PerlLogHandler> and C<PerlCleanupHandler> phases.
>
>
> and in sub-requests?

I dunno.

I also don't know if the above is true in all cases, such as when the
handler scope is per-phase. but again, I wonder how many things we depend
on (and document) change when the scope isn't for the entire request...

--Geoff


---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
Re: cvs commit: modperl-docs/src/docs/2.0/user/config config.pod [ In reply to ]
> and in response level filters! won't mod_include see these %ENV changes?

yeah, that too. sorry, I was only taking what you said at face value
because it made sense (and you nudged me to toward the docs :)

guess we still have more questions than answers at this point...

--Geoff


---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
Re: cvs commit: modperl-docs/src/docs/2.0/user/config config.pod [ In reply to ]
Geoffrey Young wrote:
>>> +Entries added to C<%ENV> are passed on to the C<subprocess_env> table,
>>> +and are thus accessible via C<r-E<gt>subprocess_env> during the later
>>> +C<PerlLogHandler> and C<PerlCleanupHandler> phases.
>>
>>
>>and in sub-requests?
>
>
> I dunno.
>
> I also don't know if the above is true in all cases, such as when the
> handler scope is per-phase. but again, I wonder how many things we depend
> on (and document) change when the scope isn't for the entire request...

That has nothing to do with perl. Once it's in subprocess_env table it's there
to stay till the end of the request. So filter, sub-requests, and latter
phases can all see the env vars via C<r-E<gt>subprocess_env> .

> yeah, that too. sorry, I was only taking what you said at face value
> because it made sense (and you nudged me to toward the docs :)

I hope at some point I won't need to nudge anybody and it'd be obvious that
it's a goodness to document some conclusions after spending all this time
figuring it out. ;)

> guess we still have more questions than answers at this point...

if you aren't sure about something, put it with a META tag, so we don't forget
that it exists and polish it later. Or may be one of the nice users will do
that for us.

__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org