Net-Async-HTTP
view release on metacpan or search on metacpan
If pipelining is active on the connection (because both the pipeline
option is true and the connection is known to be an HTTP/1.1 server),
then requests will be pipelined into the connection awaiting their
response. If not, they will be queued awaiting a response to the
previous before sending the next.
max_connections_per_host > 1
In this mode, there can be more than one connection per host. If a
new request is made, it will try to re-use idle connections if there
are any, or if they are all busy it will create a new connection to
the host, up to the configured limit.
max_connections_per_host = 0
In this mode, there is no upper limit to the number of connections
per host. Every new request will try to reuse an idle connection, or
else create a new one if all the existing ones are busy.
These modes all apply per hostname / server port pair; they do not
affect the behaviour of connections made to differing hostnames, or
differing ports on the same hostname.
PARAMETERS
The following named parameters may be passed to new or configure:
user_agent => STRING
lib/Net/Async/HTTP.pm view on Meta::CPAN
If pipelining is active on the connection (because both the C<pipeline> option
is true and the connection is known to be an HTTP/1.1 server), then requests
will be pipelined into the connection awaiting their response. If not, they
will be queued awaiting a response to the previous before sending the next.
=item max_connections_per_host > 1
In this mode, there can be more than one connection per host. If a new request
is made, it will try to re-use idle connections if there are any, or if they
are all busy it will create a new connection to the host, up to the configured
limit.
=item max_connections_per_host = 0
In this mode, there is no upper limit to the number of connections per host.
Every new request will try to reuse an idle connection, or else create a new
one if all the existing ones are busy.
=back
These modes all apply per hostname / server port pair; they do not affect the
behaviour of connections made to differing hostnames, or differing ports on
the same hostname.
=cut
$metrics->make_gauge( requests_in_flight =>
( run in 0.386 second using v1.01-cache-2.11-cpan-3cd7ad12f66 )