-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Philip M. Gollucci wrote:
> Okay, I at least understand what you are saying now.
>
> $ENV{MOD_PERL}
>
> will be in your environment even if you happen to be running a
> REGULAR CGI from /cgi-bin on mod_cgi.
Part of the problem indeed. There are other practical problems (e.g.
PerlSetupEnv Off used to disable $ENV{MOD_PERL} under mod_perl 1.3,
don't know if this is still the case). Also we may be invoking Perl
scripts from mod_perl using a piped open(), although we arguably could
mangle the %ENV by ourselves then.
Also the code purity department inside me thinks it's obvious that a
Perl notion (mod_perl version) should be materialized through a Perl
mechanism (variable or sub) instead of the UNIX env, but maybe that's
just me. No software library that I know of signals its version number
by setting an environment variable at program startup! Therefore the
whole $ENV{MOD_PERL} idea very much looks like a bad NCSA-legacy
thinko to me (mimicked from $ENV{GATEWAY_INTERFACE}, which *does*
actually make sense).
- --
Dominique QUATRAVAUX Ingénieur senior
01 44 42 00 08 IDEALX
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFC7mZgMJAKAU3mjcsRAkhdAKCxT1MDpLTeRckPN67npCCmS2Oa8gCdE5dl
N7MRmpOdCMzfzWEbCqULZJI=
=lIm8
-----END PGP SIGNATURE-----
