doc: http.Agent, reuse single socket vs new socket for each request

[ha-douken]

📗 http.Agent, reuse single socket vs new socket for each request

http.Agent documentation says
[…] It maintains a queue of pending requests for a given host and port, reusing a single socket connection for each until the queue is empty […]
Which is in contrast to the description of the maxSockets option
[…] Each request will use a new socket until the maximum is reached. []

So will it reuse a single socket connection or use a new socket for each request?

[mmomtchev]

@ha-douken In both cases - wheter keepAlive is enabled or not, maxSockets puts an upper limit to the maximum allowed concurrently running sockets. When a new request is made, whether a new socket is created, or an idle one is pulled from the pool, it is still the same limit that applies - only simultaneously running requests count.

[ha-douken]

The question is not about keepAlive and connection pools.
The question is, when a request is initiated is:
a) the request put into a pending-request-queue which is assigned to one specific connection, or
b) a new connection created dedicated to handle just this request
The docs state both which is contradictory.

I am not putting connection pools and keepAlive into the picture because it will not help the question.

[ha-douken]

Oh, darn. Does "[...] reusing a single socket connection for each [...]" mean that there is a connection per request? I read it as "the same connection is reused for each request" but maybe that is just me lacking proper english?