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

["Oleg Kalnichevski (JIRA)" <ji...@apache.org>]

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

Oleg Kalnichevski resolved HTTPASYNC-138.
-----------------------------------------
       Resolution: Fixed
    Fix Version/s: 4.1.4

Implemented in SVN 4.1.x branch

[http://svn.apache.org/viewvc?rev=1831838&view=rev]

Please review / re-test.

Oleg

 

> 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