> Example 1:
>
> I have mod_perl handlers defined for the TypeHandler and FixupHandler
> phases. If in the TypeHandler code I do this:
>
> $r->subprocess_env("TEST" => "value");
>
> Then in FixupHandler I can "see" TEST using:
>
> $something = $r->subprocess_env("TEST");
>
> Which is what yo
Geoffrey Young wrote on 5/3/04, 8:02 PM:
> > If I do the void subprocess_env trick:
> >
> > $r->subprocess()
> >
> > before retrieving $something, then it's populated along with the
> rest of
> > the environment.
>
> that only affects %ENV, not the ability of $r->subprocess_env to grab
Geoffrey Young wrote on 5/3/04, 8:02 PM:
> > Example 2:
> >
> > Basically the same except I have a C handler defined for TypeHandler
> and
> > a mod_perl handler defined for FixupHandler. When the C code does:
> >
> > ap_table_set(r->subprocess_env, "TEST", "value");
> >
> > The mod_p
> Geoff,
> So I haven't been able to get very far on the code to test this further,
> but in the Eagle book I noticed this (section 9.1.4):
>
> "subprocess_env() is only required if you need to change the environment
> in a subprocess launched by a different handler or module."
what this secti
Geoffrey Young wrote on 5/4/04, 4:18 PM:
> not really. but clearly you have some kind of problem.
Doh! I definitely do, I think I'm it.
Remember earlier when you said how in debugging you often find that you
are the bug? Well, I am the bug in this case. :-)
In the process of trying to figu
John Wittkoski wrote:
>
> Geoffrey Young wrote on 5/4/04, 4:18 PM:
>
> > not really. but clearly you have some kind of problem.
>
> Doh! I definitely do, I think I'm it.
>
> Remember earlier when you said how in debugging you often find that you
> are the bug? Well, I am the bug in this ca
