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. > 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. 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. Anyway, thanks for the input. - Perrin
