"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "lib/HTTP/DAV/Response.pm" between
HTTP-DAV-0.48.tar.gz and HTTP-DAV-0.49.tar.gz

About: HTTP-DAV (PerlDAV) is a Perl library for modifying content on Web servers using the WebDAV protocol.

Response.pm  (HTTP-DAV-0.48):Response.pm  (HTTP-DAV-0.49)
skipping to change at line 192 skipping to change at line 192
The HTTP::DAV::Response class encapsulates HTTP style responses. A response con sists of a response line, some headers, and (potentially empty) content. The HTTP::DAV::Response class encapsulates HTTP style responses. A response con sists of a response line, some headers, and (potentially empty) content.
HTTP::DAV::Response is a subclass of C<HTTP::Response> and therefore inherits it s methods. (HTTP::Response in turn inherits it's methods from C<HTTP::Message>) . HTTP::DAV::Response is a subclass of C<HTTP::Response> and therefore inherits it s methods. (HTTP::Response in turn inherits it's methods from C<HTTP::Message>) .
Therefore, this class actually inherits a rich library of functions. You are mor e likely wanting to read the C<HTTP::Response> class as opposed to this class. Therefore, this class actually inherits a rich library of functions. You are mor e likely wanting to read the C<HTTP::Response> class as opposed to this class.
Instances of this class are usually created by a C<HTTP::DAV::Resource> object a fter it has performed some request (such as get, lock, delete, etc). You use the object to analyse the success or otherwise of the request. Instances of this class are usually created by a C<HTTP::DAV::Resource> object a fter it has performed some request (such as get, lock, delete, etc). You use the object to analyse the success or otherwise of the request.
HTTP::DAV::Response was created to handle two extra functions that normal HTTP R esponses don't require: HTTP::DAV::Response was created to handle two extra functions that normal HTTP R esponses don't require:
- WebDAV reponses have 6 extra error codes: 102, 207, 422, 423, 424 and 507. Ol der versions of the LWP's C<HTTP::Status> class did not have these extra codes. These were added. - WebDAV responses have 6 extra error codes: 102, 207, 422, 423, 424 and 507. O lder versions of the LWP's C<HTTP::Status> class did not have these extra codes. These were added.
- WebDAV responses can actually contain more than one response (and often DO co ntain more than one) in the form of a "Multistatus". These multistatus responses come in the form of an XML document. HTTP::DAV::Response can accurately parse t hese XML responses and emulate the normal of the C<HTTP::Response>. - WebDAV responses can actually contain more than one response (and often DO co ntain more than one) in the form of a "Multistatus". These multistatus responses come in the form of an XML document. HTTP::DAV::Response can accurately parse t hese XML responses and emulate the normal of the C<HTTP::Response>.
HTTP::DAV::Response transparently implements these extra features without the us er having to be aware, so you really should be reading the C<HTTP::Response> doc umentation for most of the things you want to do (have I already said that?). HTTP::DAV::Response transparently implements these extra features without the us er having to be aware, so you really should be reading the C<HTTP::Response> doc umentation for most of the things you want to do (have I already said that?).
There are only a handful of custom functions that HTTP::DAV::Response returns an d those are to handle multistatus requests, C<messages()> and C<codes()>. There are only a handful of custom functions that HTTP::DAV::Response returns an d those are to handle multistatus requests, C<messages()> and C<codes()>.
The six extra status codes that DAV servers can be returned in an HTTP Response are: The six extra status codes that DAV servers can be returned in an HTTP Response are:
102 => "Processing. Server has accepted the request, but has not yet completed it", 102 => "Processing. Server has accepted the request, but has not yet completed it",
207 => "Multistatus", 207 => "Multistatus",
skipping to change at line 316 skipping to change at line 316
Takes no arguments and returns all of the messages returned in a multistatus res ponse. If called in a scalar context then all of the messages will be returned j oined together by newlines. If called in an array context the messages will be r eturned as an array. Takes no arguments and returns all of the messages returned in a multistatus res ponse. If called in a scalar context then all of the messages will be returned j oined together by newlines. If called in an array context the messages will be r eturned as an array.
$messages = $response->messages(); $messages = $response->messages();
e.g. $messages eq "Forbidden\nLocked"; e.g. $messages eq "Forbidden\nLocked";
@messages = $response->messages(); @messages = $response->messages();
e.g. @messages eq ["Forbidden", "Locked"]; e.g. @messages eq ["Forbidden", "Locked"];
This routine is a variant on the standard C<HTTP::Response> C<message()>. This routine is a variant on the standard C<HTTP::Response> C<message()>.
=back
=cut =cut
 End of changes. 2 change blocks. 
1 lines changed or deleted 3 lines changed or added

Home  |  About  |  Features  |  All  |  Newest  |  Dox  |  Diffs  |  RSS Feeds  |  Screenshots  |  Comments  |  Imprint  |  Privacy  |  HTTP(S)