X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Runtime.git;a=blobdiff_plain;f=lib%2FCatalyst%2FManual%2FIntro.pod;h=b59ad62db0717094717f74ee888c774621a517a9;hp=c237c71502425362bb94c9df6d94286fd9bf9791;hb=2ef2fb0f3a712ba1239a5fed7e332ced3bbe663f;hpb=ebfde331f96f61128105df0b2c4904cc0d5593e5

diff --git a/lib/Catalyst/Manual/Intro.pod b/lib/Catalyst/Manual/Intro.pod
index c237c71..b59ad62 100644
--- a/lib/Catalyst/Manual/Intro.pod
+++ b/lib/Catalyst/Manual/Intro.pod
@@ -485,6 +485,22 @@ Catalyst matches actions in most specific to least specific order:
 
 So Catalyst would never mistakenly dispatch the first two URLs to the '^foo$' action.
 
+=head4 B<Parameter Processing>
+
+Parameters are handled with methods in the L<Catalyst::Request>
+class. The C<param> method is functionally equivalent to the C<param>
+method of C<CGI.pm> and can be used in modules that require this.
+
+    # http://localhost:3000/catalog/view/?category=hardware&page=3
+    my $category = $c->req->param('category');
+    my $current_page = $c->req->param('page') || 1;
+
+    # multiple values for single parameter name
+    my @values = $c->req->param('scrolling_list');	    
+
+    # DFV requires a CGI.pm-like input hash
+    my $results = Data::FormValidator->check($c->req->params, \%dfv_profile);
+
 =head3 Flow Control
 
 You control the application flow with the C<forward> method, which accepts the