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 08:47:00 UTC

[jira] [Updated] (HTTPASYNC-138) PoolingNHttpClientConnectionManager doesn't allow injecting SocketAddressResolver

     [ https://issues.apache.org/jira/browse/HTTPASYNC-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Francisco A. Lozano updated HTTPASYNC-138:
------------------------------------------
    Description: 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.

> 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
>
> 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