Mailing-List: contact dev-help@hc.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpComponents Project" <dev@hc.apache.org>
Date: Sat, 5 Jan 2013 19:44:12 +0000 (UTC)
From: "Sebastiano Vigna (JIRA)" <jira@apache.org>
To: dev@hc.apache.org
Message-ID: <JIRA.12625183.1356367190436.86389.1357415052649@arcas>
In-Reply-To: <JIRA.12625183.1356367190436@arcas>
References: <JIRA.12625183.1356367190436@arcas>
Subject: [jira] [Issue Comment Deleted] (HTTPASYNC-31) There should be a
 simple way to inject a DNS resolution strategy
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Sebastiano Vigna updated HTTPASYNC-31:
--------------------------------------

    Comment: was deleted

(was: I'll add another argument in favour of DNS-resolution injection: we are experimenting a different DNS resolution behaviour depending on the platform. On Mac OS X, INetAddress.getByName() issues only a DNS lookup. But on Linux, we *always* get a reverse lookup, too. Moreover, the reverse lookup is not performed on the servers configured with sun.net.spi.nameservice.nameservers, but rather on those in resolv.conf. It's quite a mess to follow and track with tcpdump.

org.xbill.DNS.Address.getByName() does not have this problem and behaves as expected on all platforms.
)
    
> 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