Re: mod_perl/Apache question.

The mod_perl 1.x/apache 1.x combo is stable enough to power many large sites. You can rely on it. mod_perl 2 is not entirely documented or entirely ported. It is mostly there at this point, but unless you actually need one of the new features (threading, advanced filtering support) there is no reason you have to use it. In general, apache 1 is not going anywhere and most sites are not rushing to switch to apache 2, with the possible exception of Windows users (apache 2 is much better on Windows than apache 1).

So, relax. mod_perl 1 is a safe bet for a long time yet. If you're really worried about it, you can always write your application as an Apache::Registry app (Apache::Registry is a tool for running CGI scripts through mod_perl), and then it can be portable between the two systems without any changes.

Comment on Re: mod_perl/Apache question.

Replies are listed 'Best First'.
Re: Re: mod_perl/Apache question. by liz (Monsignor) on Oct 15, 2003 at 08:24 UTC
...you can always write your application as an Apache::Registry app (Apache::Registry is a tool for running CGI scripts through mod_perl), and then it can be portable between the two systems without any changes... In my opinion, you don't even have to do that. The excellent Apache::compat module mimics most of the 1.0 API on mod_perl 2.0. I've yet to have a customer that couldn't migrate without problems from 1.0 to 2.0 using that module. Liz	[reply]
Re: Re: Re: mod_perl/Apache question. by perrin (Chancellor) on Oct 15, 2003 at 15:35 UTC
That's true, but using Apache::compat is somewhat slow because of the extra work it does to emulate mod_perl 1 functions. It's meant as a temporary stopgap to port old code to mp 2. UPDATE: I asked for opinions about this on the mod_perl list, and the answer I got was that Apache::compat is problematic because it makes some code written to the actual mod_perl 2 API not work. Also, it uses a bit more memory than Registry because it loads a whole bunch of optional modules. Actual performance comparisons are hard to draw though, since it depends on which functions you use. Some functions simulated in Apache::compat are going to be significantly slower than they were in mod_perl 1, but not all of them. The full response is here.	[reply]