[
https://issues.apache.org/jira/browse/HTTPASYNC-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15167247#comment-15167247
]
Oleg Kalnichevski commented on HTTPASYNC-102:
---------------------------------------------
We had this in classic HttpClient prior to 4.3 and it turned out a very bad
idea, as it basically prevented HttpClient from working with different
connection management APIs effectively tightly coupling the client and the
connection manager interface. What we could do though is to expose
{{ConnPoolControl}} from {{HttpClient}} / {{HttpAsyncClient}} in 5.0
Oleg
> Support getConnectionManager() on HttpAsyncClient.class
> -------------------------------------------------------
>
> Key: HTTPASYNC-102
> URL: https://issues.apache.org/jira/browse/HTTPASYNC-102
> Project: HttpComponents HttpAsyncClient
> Issue Type: Improvement
> Reporter: Kalyanaraman Santhanam
>
> When the HttpAsyncClient is initialized using the Builder as follows:
> HttpAsyncClients.custom()
> .build();
> ConnectionManager is initialized to nice set of defaults.
> `https://github.com/apache/httpasyncclient/blob/4.1.x/httpasyncclient/src/main/java/org/apache/http/impl/nio/client/HttpAsyncClientBuilder.java#L647`
> However, the absence of getConnectionManager(), forces anyone who is
> interested in collecting the http stats need to initialize the
> ConnectionManager themselves.
> Which means a developer like is just going to grab the code from the
> `HttpAsyncClientBuilder` and add it my code. This defeats the purpose of
> having a `HttpAsyncClientBuilder` and prevents code reusability.
> So I want to know if there is a way to either expose the ConnectionManager or
> expose the Stats of the ConnectionManager.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
