Skip Menu |

This queue is for tickets about the HTTP-Daemon CPAN distribution.

Report information
The Basics
Id: 16812
Status: resolved
Priority: 0/
Queue: HTTP-Daemon

People
Owner: Nobody in particular
Requestors: adamk [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Unimportant
Broken in: (no value)
Fixed in: (no value)



Subject: HTTP::Daemon: [POD] Link a few more references to other classes
For thinks like the C<HTTP::Request> that refer to other classes but are only C<>s, please consider converting them to L<>s to make navigation a bit easier.
Subject: [POD PATCH] Link the references to other modules
On Fri Dec 30 12:14:49 2005, ADAMK wrote:
Show quoted text
> For thinks like the C<HTTP::Request> that refer to other classes but
> are only C<>s, please consider converting them to L<>s to make
> navigation a bit easier.

Patch attached.
Subject: link_patch.txt
--- c:\strawberry\perl\vendor\lib\LWP\UserAgent.orig 2009-10-06 15:15:34 +++ c:\strawberry\perl\vendor\lib\LWP\UserAgent.pm 2010-01-31 07:08:50 @@ -1001,1008 +1001,1008 @@ In normal use the application creates an C<LWP::UserAgent> object, and then configures it with values for timeouts, proxies, name, etc. It -then creates an instance of C<HTTP::Request> for the request that +then creates an instance of L<HTTP::Request> for the request that needs to be performed. This request is then passed to one of the request method the UserAgent, which dispatches it using the relevant -protocol, and returns a C<HTTP::Response> object. There are +protocol, and returns a L<HTTP::Response> object. There are convenience methods for sending the most common request types: get(), head() and post(). When using these methods then the creation of the @@ -1011,1015 +1011,1015 @@ The basic approach of the library is to use HTTP style communication for all protocol schemes. This means that you will construct -C<HTTP::Request> objects and receive C<HTTP::Response> objects even +L<HTTP::Request> objects and receive L<HTTP::Response> objects even for non-HTTP resources like I<gopher> and I<ftp>. In order to achieve even more similarity to HTTP style communications, gopher menus and @@ -1047,1051 +1047,1051 @@ settings are read from environment variables (see env_proxy() method below). If the C<keep_alive> option is passed in, then a -C<LWP::ConnCache> is set up (see conn_cache() method below). The +L<LWP::ConnCache> is set up (see conn_cache() method below). The C<keep_alive> value is passed on as the C<total_capacity> for the connection cache. @@ -1118,1122 +1118,1122 @@ add_cookie_header($response) methods. These methods will then be invoked by the user agent as requests are sent and responses are -received. Normally this will be a C<HTTP::Cookies> object or some +received. Normally this will be a L<HTTP::Cookies> object or some subclass. @@ -1126,1131 +1126,1131 @@ Shortcut: If a reference to a plain hash is passed in as the $cookie_jar_object, then it is replaced with an instance of -C<HTTP::Cookies> that is initialized based on the hash. This form also +L<HTTP::Cookies> that is initialized based on the hash. This form also -automatically loads the C<HTTP::Cookies> module. It means that: +automatically loads the L<HTTP::Cookies> module. It means that: $ua->cookie_jar({ file => "$ENV{HOME}/.cookies.txt" }); @@ -1141,1145 +1141,1145 @@ Get/set the headers object that will provide default header values for -any requests sent. By default this will be an empty C<HTTP::Headers> +any requests sent. By default this will be an empty L<HTTP::Headers> object. @@ -1158,1162 +1158,1162 @@ =item $ua->conn_cache( $cache_obj ) -Get/set the C<LWP::ConnCache> object to use. See L<LWP::ConnCache> +Get/set the L<LWP::ConnCache> object to use. See L<LWP::ConnCache> for details. @@ -1528,1532 +1528,1532 @@ the get() method. -This method will use the POST() function from C<HTTP::Request::Common> +This method will use the POST() function from L<HTTP::Request::Common> to build the request. See L<HTTP::Request::Common> for a details on how to pass form content and other advanced features. @@ -1553,1557 +1553,1557 @@ This method will dispatch the given $request object. Normally this -will be an instance of the C<HTTP::Request> class, but any object with +will be an instance of the L<HTTP::Request> class, but any object with a similar interface will do. The return value is a response object. See L<HTTP::Request> and L<HTTP::Response> for a description of the