You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Francisco A. Lozano (JIRA)" <ji...@apache.org> on 2018/05/18 10:24:00 UTC
[jira] [Commented] (HTTPASYNC-138)
PoolingNHttpClientConnectionManager doesn't allow injecting
SocketAddressResolver
[ https://issues.apache.org/jira/browse/HTTPASYNC-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16480466#comment-16480466 ]
Francisco A. Lozano commented on HTTPASYNC-138:
-----------------------------------------------
Just checked, and in:
[http://svn.apache.org/viewvc/httpcomponents/httpasyncclient/branches/4.1.x/httpasyncclient/src/main/java/org/apache/http/impl/nio/conn/PoolingNHttpClientConnectionManager.java?view=markup&pathrev=1831838#l184]
it seems the constructor parameter has an odd name (schemeResolver).
Other than that, I see public constructors accepting an instance of the class, so that would definitely fix it. Thanks!
> PoolingNHttpClientConnectionManager doesn't allow injecting SocketAddressResolver
> ---------------------------------------------------------------------------------
>
> Key: HTTPASYNC-138
> URL: https://issues.apache.org/jira/browse/HTTPASYNC-138
> Project: HttpComponents HttpAsyncClient
> Issue Type: Improvement
> Affects Versions: 4.1.3
> Environment:
> Reporter: Francisco A. Lozano
> Priority: Major
> Fix For: 4.1.4
>
>
> SocketAddressResolver is a public interface which seems very useful to add custom resolution logic (eg: resolve SRV records). However, PoolingNHttpClientConnectionManager doesn't allow injecting - instead, it forces InternalSocketAddressResolver. It allows to inject DnsResolver, but this is not enough.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org