Custom connection pool strategy in HttpClient

[edu-gimenez]

Hi,

Currently, I am using Vert.x 4.5.28, and due to the characteristics of my project and environment, I need to balance requests across all available connections.

I have seen that the default (and currently only) option is the LIFO selector in SharedClientHttpStreamEndpoint. This made me wonder whether it would be possible to configure the connection pool strategy for the HttpClient through HttpClientOptions.

For example, HttpClientOptions could expose an option to configure a BiFunction<PoolWaiter<HttpClientConnection>, List<PoolConnection<HttpClientConnection>>, PoolConnection<HttpClientConnection>> , which would be passed to HttpClientImpl and then to SharedClientHttpStreamEndpoint.

This would allow users to provide their own connection selector implementations when required.

If you think this makes sense, I would be happy to help by creating a PR with the necessary changes.

Thanks!

[vietj]

we could do something like this but only in Vert.x 5, since we only do 4.5.x bug fix releases

[edu-gimenez]

OK @vietj, I’m planning to migrate to Vert.x 5 soon, so that’s fine with me.