You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Oleg Kalnichevski (Jira)" <ji...@apache.org> on 2020/06/01 13:13:00 UTC
[jira] [Commented] (HTTPCLIENT-2082)
PoolingHttpClientConnectionManagerBuilder should also take the connection
socket lookup as a builder parameter
[ https://issues.apache.org/jira/browse/HTTPCLIENT-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17121003#comment-17121003 ]
Oleg Kalnichevski commented on HTTPCLIENT-2082:
-----------------------------------------------
[~rafiek] Feel free to raise a PR at GitHub with proposed changes.
Oleg
> PoolingHttpClientConnectionManagerBuilder should also take the connection socket lookup as a builder parameter
> --------------------------------------------------------------------------------------------------------------
>
> Key: HTTPCLIENT-2082
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2082
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: HttpClient (classic)
> Affects Versions: 5.0
> Reporter: Rafiek Mohamedjoesoef
> Priority: Minor
>
> Adding the connection socket lookup as a parameter for the builder makes it more flexible to use this builder.
> Example:
> {code:java}
> PoolingHttpClientConnectionManager mgr = PoolingHttpClientConnectionManagerBuilder.create()
> .setConnectionSocketFactoryRegistry(socketFactoryRegistry)
> .setSchemePortResolver(schemePortResolver)
> .setDnsResolver(dnsResolver)
> .setManagedConnPool(pool)
> .build();
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org