X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=lib%2FCatalyst%2FController%2FREST.pm;h=defe764410d5db0b664a8db3aeb951b2aed71299;hb=8bf1f20e52df6d2650bb9c5f68cca300b04a5b64;hp=99addacf7be834adff4d4b5810efac52c9841946;hpb=d3f3a2ed11595db3f5d10e8ae395a04209670356;p=catagits%2FCatalyst-Action-REST.git diff --git a/lib/Catalyst/Controller/REST.pm b/lib/Catalyst/Controller/REST.pm index 99addac..defe764 100644 --- a/lib/Catalyst/Controller/REST.pm +++ b/lib/Catalyst/Controller/REST.pm @@ -1,8 +1,8 @@ package Catalyst::Controller::REST; -use strict; -use warnings; +use Moose; +use namespace::autoclean; -our $VERSION = '0.79'; +our $VERSION = '0.91'; $VERSION = eval $VERSION; =head1 NAME @@ -36,8 +36,18 @@ Catalyst::Controller::REST - A RESTful controller # Answer PUT requests to "thing" sub thing_PUT { - ... some action ... - } + my ( $self, $c ) = @_; + + $radiohead = $c->req->data->{radiohead}; + + $self->status_created( + $c, + location => $c->req->uri->as_string, + entity => { + radiohead => $radiohead, + } + ); + } =head1 DESCRIPTION @@ -69,9 +79,11 @@ The serialization format will be selected based on the content-type of the incoming request. It is probably easier to use the L, which are described below. -The HTTP POST, PUT, and OPTIONS methods will all automatically deserialize the -contents of $c->request->body based on the requests content-type header. -A list of understood serialization formats is below. +"The HTTP POST, PUT, and OPTIONS methods will all automatically +L the contents of +C<< $c->request->body >> into the C<< $c->request->data >> hashref", based on +the request's C header. A list of understood serialization +formats is L. If we do not have (or cannot run) a serializer for a given content-type, a 415 "Unsupported Media Type" error is generated. @@ -128,7 +140,7 @@ Returns YAML generated by L. =item * C => C This uses L and L to generate YAML with all URLs turned -to hyperlinks. Only useable for Serialization. +to hyperlinks. Only usable for Serialization. =item * C => C @@ -136,6 +148,21 @@ Uses L to generate JSON output. It is strongly advised to also have L installed. The C content type is supported but is deprecated and you will receive warnings in your log. +You can also add a hash in your controller config to pass options to the json object. +For instance, to relax permissions when deserializing input, add: + __PACKAGE__->config( + json_options => { relaxed => 1 } + ) + +=item * C => C + +If a callback=? parameter is passed, this returns javascript in the form of: $callback($serializedJSON); + +Note - this is disabled by default as it can be a security risk if you are unaware. + +The usual MIME types for this serialization format are: 'text/javascript', 'application/x-javascript', +'application/javascript'. + =item * C => C Uses the L module to generate L output. @@ -245,7 +272,7 @@ such require you pass the current context ($c) as the first argument. =cut -use base 'Catalyst::Controller'; +BEGIN { extends 'Catalyst::Controller' } use Params::Validate qw(SCALAR OBJECT); __PACKAGE__->mk_accessors(qw(serialize)); @@ -376,7 +403,37 @@ sub status_no_content { my $c = shift; $c->response->status(204); $self->_set_entity( $c, undef ); - return 1.; + return 1; +} + +=item status_multiple_choices + +Returns a "300 MULTIPLE CHOICES" response. Takes an "entity" to serialize, which should +provide list of possible locations. Also takes optional "location" for preferred choice. + +=cut + +sub status_multiple_choices { + my $self = shift; + my $c = shift; + my %p = Params::Validate::validate( + @_, + { + entity => 1, + location => { type => SCALAR | OBJECT, optional => 1 }, + }, + ); + + my $location; + if ( ref( $p{'location'} ) ) { + $location = $p{'location'}->as_string; + } else { + $location = $p{'location'}; + } + $c->response->status(300); + $c->response->header( 'Location' => $location ) if exists $p{'location'}; + $self->_set_entity( $c, $p{'entity'} ); + return 1; } =item status_bad_request @@ -510,32 +567,44 @@ L. The C method uses L. The C method uses L. If you want to override either behavior, simply implement your own C and C actions -and use MRO::Compat: +and forward to another action with the Serialize and/or Deserialize +action classes: - my Foo::Controller::Monkey; - use base qw(Catalyst::Controller::REST); + package Foo::Controller::Monkey; + use Moose; + use namespace::autoclean; + + BEGIN { extends 'Catalyst::Controller::REST' } - sub begin :Private { + sub begin : Private { my ($self, $c) = @_; ... do things before Deserializing ... - $self->maybe::next::method($c); + $c->forward('deserialize'); ... do things after Deserializing ... } + sub deserialize : ActionClass('Deserialize') {} + sub end :Private { my ($self, $c) = @_; ... do things before Serializing ... - $self->maybe::next::method($c); + $c->forward('serialize'); ... do things after Serializing ... } + sub serialize : ActionClass('Serialize') {} + +If you need to deserialize multipart requests (i.e. REST data in +one part and file uploads in others) you can do so by using the +L action class. + =back =head1 A MILD WARNING I have code in production using L. That said, it is still under development, and it's possible that things may change -between releases. I promise to not break things unneccesarily. :) +between releases. I promise to not break things unnecessarily. :) =head1 SEE ALSO @@ -560,4 +629,6 @@ You may distribute this code under the same terms as Perl itself. =cut +__PACKAGE__->meta->make_immutable; + 1;