When building an HTTP client, we should be able to configure the maximum idle connection pool size in order to ensure we don't keep an excess of open connections. Open connections consume resources on the downstream target systems, and we generally don't need a huge amount of concurrency by default.
We should be able to trivially add support for this by simply exposing a method to forward to Builder::pool_max_idle_per_host.
Context
When building an HTTP client, we should be able to configure the maximum idle connection pool size in order to ensure we don't keep an excess of open connections. Open connections consume resources on the downstream target systems, and we generally don't need a huge amount of concurrency by default.
We should be able to trivially add support for this by simply exposing a method to forward to
Builder::pool_max_idle_per_host.