> Untill > now, with a few little changes or sometimes with no changes at all > (depending on what API was used) they could have the code running under > mp1 and mp2. With this rename they either need to split their code and > maintain different versions, which are otherwise identical, or have an > unmaintable code at best.
I just don't believe this at all, but let's examine it. from a strict "mp1 -> using mp2 for the absolute first time" how does a rename to Apache2:: make things worse? from what I can see it's only these three cases - mod_perl2.pm, which is almost never called by name in any program - Apache2->request, which has caveats in mp2 anyway, so doesn't directly port - Apache2->server in my mind even the sum of these pales in comparison to the changes all authors will need to do wrt "the 50 million modules I need to use() just to get my app working with mp2." so, what specifically did you have in mind, on this single issue, when you say that a rename will make matters worse than they are now? --Geoff --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
