[Catalyst-commits] r8842 - trunk/examples/CatalystAdvent/root/2008/pen

[zarquon at dev.catalyst.perl.org]

Author: zarquon
Date: 2008-12-12 10:45:48 +0000 (Fri, 12 Dec 2008)
New Revision: 8842

Modified:
   trunk/examples/CatalystAdvent/root/2008/pen/12.pod
Log:
light edits

Modified: trunk/examples/CatalystAdvent/root/2008/pen/12.pod
===================================================================
--- trunk/examples/CatalystAdvent/root/2008/pen/12.pod	2008-12-12 10:45:12 UTC (rev 8841)
+++ trunk/examples/CatalystAdvent/root/2008/pen/12.pod	2008-12-12 10:45:48 UTC (rev 8842)
@@ -1,13 +1,13 @@
 =head1 Custom URL styles with CatalystX::CRUD
 
-A recurring discussion in the Catalyst community revolves
-around best practices for URL construction. The Chained feature
-can make URLs fun (and so elegant!) to construct in your Controller code.
-But what should they look like to the user?
+A recurring discussion in the Catalyst community revolves around best
+practices for URL construction. The Chained feature can make URLs fun
+(and so elegant!) to construct in your Controller code.  But what
+should they look like to the user?
 
-RESTful CRUD URLs are an increasingly common (and therefore contentious)
-exercise. What's the proper way to create, read, update and delete your
-precious data?
+RESTful CRUD URLs are an increasingly common (and therefore
+contentious) practice. What's the proper way to create, read, update
+and delete your precious data?
 
 L<CatalystX::CRUD> offers two different URL styles out-of-the-box.
 The RPC-style looks like:
@@ -29,39 +29,41 @@
  /user/joe/edit_form # edit joe
  /user/joe           # PUT/POST joe
  /user/joe           # DELETE joe
- 
-And the L<CatalystX::CRUD::REST> Controller offers an RPC-compat
-config option as well, so that either style works.
 
+The L<CatalystX::CRUD::REST> Controller offers an RPC-compat config
+option as well, so that either style works.
+
 But the special reserved method names in the Controllers mean that
 you can't have a user named C<search>, C<create> or C<list>. And that
 seems to rankle some folks, who would prefer a URL convention like:
 
  /user/id/joe        # GET joe
  /user/id/joe/save   # POST joe
- 
-With that extra C</id> in there, there are no reserved words when dealing
-with user instances. Cleaner, yes, at the expense of a little URL length.
 
-Here's a quick way to customize your CatalystX::CRUD instance URLs to add
-that extra C</id> (or whatever) into your URLs to appease your sense
-of URL correctness.
+With the extra C</id> in there, there are no reserved words when
+dealing with user instances. Cleaner, yes, at the expense of a little
+URL length.
 
-The PathPrefix hack was first introduced by Brian Cassidy, who deserves
-mad props for the simple genius. The effect is to make your initial
-Chained starting method match the namespace of the current controller, so
-that you can move your controllers around and not have to rewrite any code
-(which is what makes L<CatalystX::CRUD::Controller> subclasses work).
-The original looks like:
+Here's a quick way to customize your CatalystX::CRUD instance URLs to
+add that extra C</id> (or whatever) into your URLs to appease your
+sense of URL correctness.
 
+The PathPrefix hack was first introduced by Brian Cassidy, who
+deserves mad props for his simple genius. The effect is to make your
+initial Chained starting method match the namespace of the current
+controller, so that you can move your controllers around and not have
+to rewrite any code (which is what makes
+L<CatalystX::CRUD::Controller> subclasses work).  The original looks
+like:
+
  sub _parse_PathPrefix_attr {
     my ( $self, $c, $name, $value ) = @_;
     return PathPart => $self->path_prefix;
  }
 
-Override _parse_PathPrefix_attr() in your controller and you can 
-append whatever you want to the path_prefix() to get
-the desired effect:
+Override _parse_PathPrefix_attr() in your controller and you can
+append whatever you want to the path_prefix() to get the desired
+effect:
 
  sub _parse_PathPrefix_attr {
     my ( $self, $c, $name, $value ) = @_;