I don't know the full story, but I am pretty sure that the movers and shakers in the decision team have a strong point for it (possibly documented in perl.apache.org). It's caused me unexpected pain recently as well; and I have to spend today as well working through my codes because of it. But I am glad that people like Randy, Markus, and the documentation team (@perl.apache.org) have jumped in to help stranded people like me ('cos my job depends on my product!). Thanks guys!

The shortest version I can give for in explanation us

- mod_perl2 is a new API compared to mod_perl1
- The implementation was kept in the same Apache:: namespace
- It was demonstrated that this caused some large long term problems
- Most were unfixable once mod_perl2 became "stable and supported"
- The most favoured solution was to move to Apache2::
- This would cause pain for early adopters (but only once)
- Final decision was to let early adopters "take the hit" now, to prevent the long term problems on the entire userbase.


My only wish is that there will be no more changes to the libraries in such extent. After all, if this is the best way to move (mod_)perl forward, we must all bite the bullet at one time or another.

Yes, it's a one time only change.

Adam K

Reply via email to