Doug MacEachern wrote:
> On Tue, 4 Jun 2002, Stas Bekman wrote:
> 
> 
>>[EMAIL PROTECTED] wrote:
>>
>>
>>>  -C<GATEWAY_INTERFACE> - is always set to something like: C<CGI-Perl/1.1>
>>>  +C<GATEWAY_INTERFACE> - is set to C<CGI-Perl/1.1> for compatibility
>>>  +with mod_perl 1.x. The C<MOD_PERL> environment variable has existed
>>>  +since 1.17 and is recommended over checking the contents of
>>>  +C<GATEWAY_INTERFACE>.
>>
>>shouldn't it be better to have GATEWAY_INTERFACE documented as 
>>deprecated in 2.0?
 >
> i think he pretty much did that without using the word 'deprecated'.
> but using that word would be fine of course.

Good.

I look at the 2.0 documentation in a different light. After awhile we 
will have many new users whose first mod_perl experience was 2.0, so I 
see no reason why burdening docs with references to 1.x, which in a long 
run will be irrelevant anyway. That's why I'm concentrating all the 
"migration" notes in user/compat/compat.pm and devel/compat/compat.pm, 
so those interested in migration will read those docs.


>>I suggest to kill it completely and only set in Apache::compat. Can we?
> 
> 
> not really.  it would require that Apache::compat is loaded at startup, 
> otherwise %ENV is restored to what it was before the request (minus 
> GATEWAY_INTERFACE) and it will never get set again since Apache/compat.pm 
> is in %INC.  granted the suggested way to load Apache::compat is at 
> startup, our tests do not do that and there no reason we shouldn't support 
> modules that do:
> 
> package Apache::Foo;
> 
> eval { require Apache::compat };
> 
> ...
> 
> 1;

Again, I didn't think that Apache::compat might not be loaded at 
startup. sure, you are right.

Thanks!


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


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to