Hi!
Recently, I was /using/ the docs once again, and I stumbled on the Code Snippet "mod_rewrite in Perl" (docs/1.0/guide/snippets.html#toc_mod_rewrite_in_Perl)
One year ago, I wrote a module that does exactly that. It's on CPAN, called CGI::URI2param and includes a PerlInitHandler for mod_perl support (Apache::URI2param).
So, two questions:
1: Would it make sense to link to this module from this section, and - more generally - would it make sense to link to CPAN-modules implementing some of those snippets.
+1. That's clearly the best way... Teach how it's done, so that people can learn, and then point to what they should *really* use. Go ahead with patches.. I tried to do the same with Lincoln's tricks tutorial, because there are *many* snippets in it, but some are CPAN modules now, and so should be used.
2: In the example, $r->args is used to set the value. I am using $r->param (together with Apache::Request->instance). Would $r->args be better suited?
Oops. I was going to say "use $r->param etc etc.." because I thought you meant getting the value... Well, the problem is that if the user of your module isn't using Apache::Request, you're mildly screwed as your params won't pass on. For example if he uses CGI.pm, he won't get your params. So it might be a better idea to reconstruct the query string in some way and set $r->args, which will then be reparsed during the content handling... This however you might be able to do directly with Apache::Request or CGI.pm, I don't know really.
-- Per Einar Ellefsen [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
