Client set max connection about http-client

[rdlowrey]

Well, the first order of business is that this setting only limits the number of connections on a per-host basis -- it doesn't limit all connections. Are you observing this behavior for a single host? I.E. if you you request www.google.com many times at once do you see the same thing?

This configuration basically exists to prevent me from getting IP bans from hammering the same hosts with tons of connections at once. When making many concurrent requests to the same host our connections are "checked-in" and "checked-out" with individual requests queued until a connection to the host in question is available.

Second, a new read watcher is created inside the Client class each time a socket connection is checked out. This is expected. The alternative would be to map a single watcher to each socket, but this approach would require the underlying socket lib (Acesync) to notify the client class each time an idle connection was closed.

If you wish to verify that new connections aren't being created in excess of the OP_HOST_CONNECTION_LIMIT you can add some basic print debugging here.

[rdlowrey]

I'm closing this for now. Please let me know if you still believe this is an issue.