Perrin Harkins wrote:
On Wed, 2003-10-15 at 15:13, Stas Bekman wrote:

The biggest problem with Apache::compat is that it modifies the behavior of several methods to behave like they did in mp1. So if you run on the same server some code that relies on their mp2 behavior, there is a conlict.


That makes sense.  So, it can be difficult to move code over one piece
at a time in this way because using Apache::compat can prevent your
ported code from working.

True. Perhaps we need to move those methods into another module, or have a special import() rule to enable them. Josh has suggested categories some time ago, but nobody implemented them, so it remains an idea. Scott has suggested using source filter to scope the usage of the APIs coming from Apache::compat, (ala use/no Apache::compat), but neither I or someone else had a chance to implement the suggested technique.


Besides that memory-wise it'll just load all the modules that it needs, so you might get some unneeded modules loaded, which shouldn't be much of a problem.


That's what I figured.  I don't have a mp 2 build handy at the moment to
try this with, but I'm assuming it's not a big hit because the modules
are at least preloaded.

That's correct.


It's kind of a tough call what to recommend.  He's a mod_perl newbie, so
I don't feel comfortable suggesting he start with mp 2 at the moment.
Ultimately the best approach is probably to write for mp 1 now, and port
it in a few years with the help of compat, but Registry is a tempting
alternative for applications that are not really using the Apache API.

Not at all, mp2 1.99_10 is very robust (at least according to our test suite), and the we mainly haven't finalized the API for new features, the features coming from mp1 are pretty much the same (assuming Apache 2.0 kept the API) and won't change. Since most people want mod_perl for its PerlResponseHandler I think most newbies will be just fine with mp2, while using the books/docs for mp1 and what's available for mp2. Especially as you mention for Registry scripts.


__________________________________________________________________
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



Reply via email to