X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=README;h=4647747600c8116e62e05349465ccfc450eb9645;hb=be3c588afb1dd6d6c8e6171c01c3d38afa75d6d5;hp=8da598bc561129e438f43c437d26d365b88389ce;hpb=8f00a41bd7efb75d302d0a333e0eb5bc7d75c931;p=catagits%2FCatalyst-Action-REST.git

diff --git a/README b/README
index 8da598b..4647747 100644
--- a/README
+++ b/README
@@ -135,14 +135,24 @@ AVAILABLE SERIALIZERS
 
         { data => $yourdata }
 
+    View
+      Uses a regular Catalyst view. For example, if you wanted to have your
+      "text/html" and "text/xml" views rendered by TT:
+
+              'text/html' => [ 'View', 'TT' ],
+              'text/xml'  => [ 'View', 'XML' ],
+        
+      Will do the trick nicely.
+
     By default, Catalyst::Controller::REST will return a "415 Unsupported
     Media Type" response if an attempt to use an unsupported content-type is
     made. You can ensure that something is always returned by setting the
     "default" config option:
 
-       __PACKAGE__->config->{'serialize'}->{'default'} = 'YAML';
+       __PACKAGE__->config->{'serialize'}->{'default'} = 'text/x-yaml';
 
-    Would make it always fall back to YAML.
+    Would make it always fall back to the serializer plugin defined for
+    text/x-yaml.
 
     Implementing new Serialization formats is easy! Contributions are most
     welcome! See Catalyst::Action::Serialize and
@@ -259,8 +269,7 @@ IMPLEMENTATION DETAILS
         ],
                     'text/x-config-general' => [ 'Data::Serializer', 'Config::General' ]
         ,
-                    'text/x-php-serialization' => [ 'Data::Serializer', 'PHP::Serializat
-        ion' ],
+                    'text/x-php-serialization' => [ 'Data::Serializer', 'PHP::Serialization' ],
                   },
               }
           );