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.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.