From: Frank Lichtenheld Date: Tue, 3 Jun 2008 21:09:54 +0000 Subject: fix several syntax problems in POD and some typos --- lib/REST/Application.pm | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/lib/REST/Application.pm b/lib/REST/Application.pm index 7298ef0..c5ed22b 100644 --- a/lib/REST/Application.pm +++ b/lib/REST/Application.pm @@ -514,7 +514,7 @@ L - A framework for building RESTful web-applications. =head1 SYNOPSIS - # MyRESTApp L instance / mod_perl handler + # MyRESTApp REST::Application instance / mod_perl handler package MyRESTApp; use Apache; use Apache::Constants qw(:common); @@ -640,7 +640,9 @@ redundant). So, when writing a subroutine handler you'd do: The handler is processed and should return a string or a scalar reference to a string. Optionally the handler should set any header information via the -C method on instance object pased in. +C method on instance object passed in. + +=back =head1 CALLING ORDER @@ -701,8 +703,6 @@ For example, if you wanted to have your code branch on the entire URI of the HTTP request rather than just the path info you'd merely overload C to return the URI rather than the path info. -=back - =head1 METHODS =head2 new(%args) @@ -758,7 +758,7 @@ false. The array is expected to be two elements long, the first element is a class name or object instance. The 2nd element is a method name on that -class/instance. IF the 2nd element is ommitted then the method name is assumed +class/instance. IF the 2nd element is omitted then the method name is assumed to be the same as the B, e.g. C, C, whatever. =item hash ref @@ -770,7 +770,7 @@ specified as '*', in which case that is used if a more specific match is not found. It is possible for the value of the handler to be another hash ref, rather than -one of the four above types. In this case it is assumed content-negotion is +one of the four above types. In this case it is assumed content-negotiation is wanted. The keys of this second hash are MIME types and the values are one of the four above types. For example: @@ -819,7 +819,7 @@ This method returns the headers as a string. =head2 sendRepresentation($representation) -This method just returns C<$representation>. It is provided soely for +This method just returns C<$representation>. It is provided solely for overloading purposes. =head2 headerType([$type]) @@ -835,8 +835,8 @@ arguments then it simply returns the current header values as a hash, where the keys are the header fields and the values are the header field values. If this method is called multiple times then the values of %args are additive. -So calling C<$self->header(-type => "text/html")> and C<$self->header(-foo => -"bar")> results in both the content-type header being set and the "foo" header +So calling C<$self-Eheader(-type =E 'text/html')> and C<$self-Eheader(-foo =E +'bar')> results in both the content-type header being set and the "foo" header being set. =head2 resetHeader() @@ -854,7 +854,7 @@ overloading. Given a list of MIME types this function returns the best matching type considering the Accept header of the current request (as returned by -C. +C). =head2 simpleContentNegotiation(@types) @@ -906,7 +906,7 @@ POST can be used to tunnel anything. =head1 AUTHORS -Matthew O'Connor Ematthew@canonical.org +Matthew O'Connor Ematthew@canonical.orgE =head1 LICENSE