Doug MacEachern wrote:
> On Tue, 9 Apr 2002, Stas Bekman wrote:
> 
> 
>>1. The chdir issue with registry isn't resolved yet, need to do 
>>something about it before mod_perl 2.0 will be really useful for people, 
>>since want it or not, there are many users who want only the registry 
>>interface.
> 
> 
> sure, but not everybody using registry relies on using '.' in @INC or
> open "./foo";  @INC is easy to solve, just adding cwd to it for that 
> request.  

I'm not sure that's a good idea. It may break someone's code, who didn't 
expect the cwd to be in @INC. should the control to automatically 
prepand to @INC be given to users here?

> open, exec, system, etc., that rely on '.' seems nasty to fix.
> users could change code for example, from:
> open "./foo";
> to:
> use File::Basename;
> my $cwd = basename $0;
> open "$cwd/foo";
> 
> that'd work with both modperl and cgi.

what if their code is doing chdir? do we simply say, you have to get rid 
of chdirs, no matter what?

>>2. should we revert back to Apache::Registry from ModPerl::Registry, now 
>>that we have:
>>
>>   use Apache2
> 
> 
> the current module names should stay.  in part since the 1.x stuff will 
> run with 2.0 if Apache::compat is loaded.  a wrapper might be nice, but 
> i'd rather wait a bit to see if people actually complain about have to 
> change Apache::Registry to ModPerl::Registry in the config file.
> 
> the compat goal has always focused on keeping 1.x _code_ running in 2.0.
> having to change config files is acceptable.

sure, let's wait. I was thinking that if the new registry comes as a drop
in replacement, there is no need for a new name. It should run 1.x registry
code the same way. the issues with chdir are the same with 
Apache::Registry.

Oh, wait, users *cannot* use Apache::Registry from 1.x with threaded mpm 
by definition since it does chdir to the scripts dir.


__________________________________________________________________
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