On Jan 2, 2005, at 11:12 AM, Joe Schaefer wrote:
I don't think we'd have too much trouble getting comfortable with a "mod_perl" -> "mod_perl2" rename, but the difficult question is what to do about Apache::. A rename may make sense for the bare-metal libraries like Apache::Request (what to actually call it is a different issue, because the 2.x version is really an APR:: application).
APR::Request?
But a rename wouldn't make sense for something like Apache::ASP.
Those of us who use Apache apps would have to do something like this:
eval "use Apache2"; use Apache if $@;
If we wrote our apps to the Apache1 API, we could perhaps use some sort of Apache2::compat module to ensure backwards compatibility. Otherwise, we might have to use some if/then statements. But if my use of mp1 is any indication, that wouldn't be too much work.
Waiting for King Solomon to appear isn't going to lead us anywhere. The community needs an actionable proposal to kick around if you're pining for real change.
I'm not pining for real change. I'm pining for an open and welcome cheer from all parties upon the release of mp2. With the current approach, we're clearly not going to get it, and that will be to the detriment of mp2. I think that would be sad, and am willing to make sacrifices in how I have to maintain my own code (to be compatible or not) in order to avoid it. I suspect that other modules authors who use the mp API would agree.
Regards,
David
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
