This is going to be quick...

I got my start with mod_perl several years ago after lots of fits and starts, and after awhile got proficient in using it for web-based applications under Apache 1.3.xx

Now I've had to begin thinking about migrating to Apache2. I realize there are quite a few things that aren't working in Apache2 that work in Apache, but I can work around those with some of the newer modules (there are very specific things in SSL that Apache2 broke which works under Apache, as well as a few other quirks).

Under Apache, I used to use Apache::Request to catch the param() being passed in the URI field (or CGI.pm in quick cases), by using $apr->param('foo');. I used a dispatch table to switch into the proper sub when the proper param was passed. sub 'dl' for param 'dl' and so on, and I catch false/non-existant params and handle those as well.

Now I need to find "The Best™" way to keep catching param() as passed to my script under Apache2 and mod_perl2.

With atcroft's help, I found the mod_perl2 user's guide, but I'm looking for alternatives or better solutions to catch param(). I am rebuilding a pretty complicated CMS I wrote from the ground up, and would like to get this right when I start, not after I go into production (as I did when migrating from CGI to Apache::Request in the original version of the portal system).

Any snippets/modules/theories I should consider here?