Doug MacEachern wrote:

> great!  i haven't reviewed yet (and will need some time to).  i should
> have mentioned this thought earlier, but it would make the dev/transition
> much easier if the new kit has new names (i.e. other than
> Apache::{Registry,PerlRun}).  the 1.x stuff currently works with
> Apache::compat.  how much trouble would it be for you to rename things?
> could be as easy as calling it ModPerl:: instead of Apache::
> then you could go ahead and commit, hack on it, etc., while people will
> still be able to use the working 1.x versions.
> what do you think?

Sure, that's very easy to do ;)

So you suggest to just rename the leading package s/Apache/ModPerl/ but 
to keep the Registry, PerlRun, RegistryNG and RegistryBB names? They 
preserve exactly the same functionality.

We have discussed this before a bit, it's about the rest of the Apache:: 
modules, whether they should keep the same names or change. It seems 
that you've changed your mind, since originally you said that none of 
the modules will have to change their names when ported to 2.x.

The only problem we have is that some servers will need 1.x and 2.x live 
under the same perl/lib tree. I'm still not sure how this is going to 
happen if we keep the same names, and put the burden on the developers 
to make their modules working with 1.x. and 2.x.

As for the registry stuff, there are still a few things that need to be 
resolved before we can drop Apache::compat for the registry, but I 
wanted the basic code to be in CVS and get the initial response on 
whether I'm going in the right direction.


_____________________________________________________________________
Stas Bekman             JAm_pH      --   Just Another mod_perl Hacker
http://stason.org/      mod_perl Guide   http://perl.apache.org/guide
mailto:[EMAIL PROTECTED]  http://ticketmaster.com http://apacheweek.com
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/


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

Reply via email to