From the mod_perl 1.0 land:
http://perl.apache.org/docs/1.0/guide/ performance.html#Apache__args_vs__Apache__Request__param_vs__CGI__param
And there was a report recently on the apreq-dev list, which shows an even better performance of apreq under Apache2.
Thanks Stas.
I understand the benefits of a C binding to the Apache API over, say, CGI.pm processing using the environment vars (which is why all my projects use libapreq 1). But since both mod_perl2's Apache::RequestRec and libapreq's Apache::Request implement XS glue to the Apache API (as far as I can tell), I meant to ask about that relationship. Is Apache::RequestRec under 2 analogous to Apache::args under 1?
To make the question shorter, is apreq expected to be the preferred interface for mod_perl 2, as it was for mod_perl 1? (I'd hate for anyone to cross the Spirits of Tim Toady. Just wondering about the sentiment of the list.)
Thanks, Dan Brian
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
