HTTPClient: Needs better pooling configurations

[jentfoo]

HTTPClient will always create a connection if it is not available. There is no way to specify a maximum connection limit (waiting till one becomes available). There is also no way to set things like maximum connection lifetimes and have them closed / expired if needed.

[lwahlmeier]

HTTPClient does allow you to set the the max connections, just not the max per host, is that what you mean? If so it should be pretty easy to add, I have never had a need for this, but I could see uscases for it.

Connection lifetimes can be set through the setTimeout, granted its a global option for the client, but it will cause requests to timeout if they are not completed with in a certain amount of time. We might be able to set it in the httprequest object instead though I still have the same concerns about having state in those objects thats not really part of the httpRequest (really gets messy when thinking of the parsing/building of them on the server side).

I think you might mean there is no time out for how long we will hold connections to a server endpoint even after the request is completed? And that is true, though those connections will be closed as the pool/max connection limit is hit, or if the server times them out/closes them. It should be pretty simple to set a max keepalive if needed though.

[jentfoo]

HTTPClient does allow you to set the the max connections

Is this true? I only see max concurrent requests, not max connections in the pool

I think you might mean there is no time out for how long we will hold connections to a server endpoint even after the request is completed? And that is true

Yes this, is part of what I was indicating would be good to add