> that's a different test ;) and that's not what you said. You said:
>
>>>well, knowing how apache works it was definitely a surprise when I
>>>>> looked at
>>>>> subenv.t
>> ...
>> no, that $r->subprocess_env(MYFOO => 1) magically set $ENV{FOO}. I
> wasn't
>> expecting that.
yes, yes, I was getting all confused :)
>
> Here it's the opposite, %ENV affects $r->subprocess_env, but not the
> other way around.
> It's not "tied" per se. It just affects subprocess_env. I think it's a
> good thing. Consider a CGI script setting %ENV wants to affect a log
> handler (but can't use modperl api), which can now always get the env
> var via $s->subprocess_env (whether the previous phase was using %ENV or
> subprocess_env to set it).
ok, when I saw it happen in one direction, I assumed they were officially tied.
and I see your point wrt loggers.
> BTW, It happens only during the response phase, only for 'perl-script',
> and not for 'modperl' (see modperl_env_request_tie /
> modperl_env_request_untie in mod_perl.c).
that's even better. actually, letting %ENV population drizzle down to
subprocess_env only during content-generation is a rather nice feature.
so, all is cool with me. sorry it took up so much bandwidth to get things
straight in my head.
--Geoff
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
