| 1 |
From: Frank Lichtenheld <[email protected]> |
| 2 |
Date: Tue, 3 Jun 2008 21:09:54 +0000 |
| 3 |
Subject: fix several syntax problems in POD and some typos |
| 4 |
|
| 5 |
--- |
| 6 |
lib/REST/Application.pm | 22 +++++++++++----------- |
| 7 |
1 file changed, 11 insertions(+), 11 deletions(-) |
| 8 |
|
| 9 |
diff --git a/lib/REST/Application.pm b/lib/REST/Application.pm |
| 10 |
index 7298ef0..c5ed22b 100644 |
| 11 |
--- a/lib/REST/Application.pm |
| 12 |
+++ b/lib/REST/Application.pm |
| 13 |
@@ -514,7 +514,7 @@ L<REST::Application> - A framework for building RESTful web-applications. |
| 14 |
|
| 15 |
=head1 SYNOPSIS |
| 16 |
|
| 17 |
- # MyRESTApp L<REST::Application> instance / mod_perl handler |
| 18 |
+ # MyRESTApp REST::Application instance / mod_perl handler |
| 19 |
package MyRESTApp; |
| 20 |
use Apache; |
| 21 |
use Apache::Constants qw(:common); |
| 22 |
@@ -640,7 +640,9 @@ redundant). So, when writing a subroutine handler you'd do: |
| 23 |
|
| 24 |
The handler is processed and should return a string or a scalar reference to a |
| 25 |
string. Optionally the handler should set any header information via the |
| 26 |
-C<header()> method on instance object pased in. |
| 27 |
+C<header()> method on instance object passed in. |
| 28 |
+ |
| 29 |
+=back |
| 30 |
|
| 31 |
=head1 CALLING ORDER |
| 32 |
|
| 33 |
@@ -701,8 +703,6 @@ For example, if you wanted to have your code branch on the entire URI of the |
| 34 |
HTTP request rather than just the path info you'd merely overload |
| 35 |
C<getMatchText()> to return the URI rather than the path info. |
| 36 |
|
| 37 |
-=back |
| 38 |
- |
| 39 |
=head1 METHODS |
| 40 |
|
| 41 |
=head2 new(%args) |
| 42 |
@@ -758,7 +758,7 @@ false. |
| 43 |
|
| 44 |
The array is expected to be two elements long, the first element is a class |
| 45 |
name or object instance. The 2nd element is a method name on that |
| 46 |
-class/instance. IF the 2nd element is ommitted then the method name is assumed |
| 47 |
+class/instance. IF the 2nd element is omitted then the method name is assumed |
| 48 |
to be the same as the B<REQUEST_METHOD>, e.g. C<GET()>, C<PUT()>, whatever. |
| 49 |
|
| 50 |
=item hash ref |
| 51 |
@@ -770,7 +770,7 @@ specified as '*', in which case that is used if a more specific match is not |
| 52 |
found. |
| 53 |
|
| 54 |
It is possible for the value of the handler to be another hash ref, rather than |
| 55 |
-one of the four above types. In this case it is assumed content-negotion is |
| 56 |
+one of the four above types. In this case it is assumed content-negotiation is |
| 57 |
wanted. The keys of this second hash are MIME types and the values are one of |
| 58 |
the four above types. For example: |
| 59 |
|
| 60 |
@@ -819,7 +819,7 @@ This method returns the headers as a string. |
| 61 |
|
| 62 |
=head2 sendRepresentation($representation) |
| 63 |
|
| 64 |
-This method just returns C<$representation>. It is provided soely for |
| 65 |
+This method just returns C<$representation>. It is provided solely for |
| 66 |
overloading purposes. |
| 67 |
|
| 68 |
=head2 headerType([$type]) |
| 69 |
@@ -835,8 +835,8 @@ arguments then it simply returns the current header values as a hash, where the |
| 70 |
keys are the header fields and the values are the header field values. |
| 71 |
|
| 72 |
If this method is called multiple times then the values of %args are additive. |
| 73 |
-So calling C<$self->header(-type => "text/html")> and C<$self->header(-foo => |
| 74 |
-"bar")> results in both the content-type header being set and the "foo" header |
| 75 |
+So calling C<$self-E<gt>header(-type =E<gt> 'text/html')> and C<$self-E<gt>header(-foo =E<gt> |
| 76 |
+'bar')> results in both the content-type header being set and the "foo" header |
| 77 |
being set. |
| 78 |
|
| 79 |
=head2 resetHeader() |
| 80 |
@@ -854,7 +854,7 @@ overloading. |
| 81 |
|
| 82 |
Given a list of MIME types this function returns the best matching type |
| 83 |
considering the Accept header of the current request (as returned by |
| 84 |
-C<getAcceptHeader()>. |
| 85 |
+C<getAcceptHeader()>). |
| 86 |
|
| 87 |
=head2 simpleContentNegotiation(@types) |
| 88 |
|
| 89 |
@@ -906,7 +906,7 @@ POST can be used to tunnel anything. |
| 90 |
|
| 91 |
=head1 AUTHORS |
| 92 |
|
| 93 |
-Matthew O'Connor E<lt>[email protected]<gt> |
| 94 |
+Matthew O'Connor E<lt>[email protected]<gt> |
| 95 |
|
| 96 |
=head1 LICENSE |
| 97 |
|