hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebastiano Vigna (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HTTPASYNC-31) There should be a simple way to inject a DNS resolution strategy
Date Mon, 24 Dec 2012 16:40:12 GMT
Sebastiano Vigna created HTTPASYNC-31:
-----------------------------------------

             Summary: There should be a simple way to inject a DNS resolution strategy
                 Key: HTTPASYNC-31
                 URL: https://issues.apache.org/jira/browse/HTTPASYNC-31
             Project: HttpComponents HttpAsyncClient
          Issue Type: Improvement
    Affects Versions: 4.0-beta3
            Reporter: Sebastiano Vigna


With DefaultHttpClient it is not difficult to use a custom DNS resolution strategy (e.g.,
DNSJava) by using a
specialized DefaultConnectionOperator. Doing the same with the asynchronous client presently
is very difficult as it requires to create an entirely new connection manager (and the standard
implementation uses many package-accessible implementations, so this requires modifying the
actual HttpAsyncClient distribution). For a client able to open simultaneously thousands of
connections careful DNS management is essential.

Of course it is in principle possible to use a local installation of BIND etc., but it would
be nice to be able to do configurable DNS caching in pure Java.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org


Mime
View raw message