--- AnyEvent-HTTP/README 2009/07/07 00:15:32 1.8 +++ AnyEvent-HTTP/README 2009/08/05 16:43:47 1.10 @@ -92,7 +92,8 @@ The request headers to use. Currently, "http_request" may provide its own "Host:", "Content-Length:", "Connection:" and "Cookie:" headers and will provide defaults for "User-Agent:" - and "Referer:". + and "Referer:" (this can be suppressed by using "undef" for + these headers in which case they won't be sent at all). timeout => $seconds The time-out to use for various stages - each connect attempt @@ -104,8 +105,8 @@ then the default proxy (as specified by $ENV{http_proxy}) is used. - $scheme must be either missing or "http" for HTTP, or "https" - for HTTPS. + $scheme must be either missing, "http" for HTTP or "https" for + HTTPS. body => $string The request body, usually empty. Will be-sent as-is (future @@ -176,7 +177,10 @@ processed incrementally. It is usually preferred over doing your own body handling via - "want_body_handle". + "want_body_handle", but in case of streaming APIs, where HTTP is + only used to create a connection, "want_body_handle" is the + better alternative, as it allows you to install your own event + handler, reducing resource usage. want_body_handle => $enable When enabled (default is disabled), the behaviour of @@ -199,7 +203,7 @@ JSON/XML stream). If you think you need this, first have a look at "on_body", to - see if that doesn'T solve your problem in a better way. + see if that doesn't solve your problem in a better way. Example: make a simple HTTP GET request for http://www.nethype.de/ @@ -245,7 +249,7 @@ +http://software.schmorp.de/pkg/AnyEvent)"). $AnyEvent::HTTP::MAX_PER_HOST - The maximum number of concurrent conenctions to the same host + The maximum number of concurrent connections to the same host (identified by the hostname). If the limit is exceeded, then the additional requests are queued until previous connections are closed.