On Mon, 3 Jun 2002, Doug MacEachern wrote:

> On Mon, 3 Jun 2002, Stas Bekman wrote:
> 
> > I was documenting the env vars set under 2.0, and saw that 
> > GATEWAY_INTERFACE shouldn't be available under 2.0 unless MP_COMPAT_1X 
> > is defined. But it's always defined. What's the plan?
> 
> it is mainly for documentation at the moment.  anything withing 
> MP_COMPAT_1X would not be 2.0 if we didn't not want to be compatible with 
> 1.x.  and at somepoint there may be an option to disable things within if 
> one does not require the compat.

Meaning that we do want to be compatible with 1.x? and we don't mind to 
have these bits, since they don't take much space and don't add to the 
overhead (well mostly, e.g. you do set GATEWAY_INTERFACE).

So Apache::compat is optional but not the configuration directives and a
few other bits?

So should I change the docco:
http://perl.apache.org/release/docs/2.0/user/compat/compat.html#Configuration_Files_Porting

to say that the listed items are deprecated in 2.0, but still available? 
Or just keep it as is?

__________________________________________________________________
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