Return-Path: Mailing-List: contact commons-httpclient-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list commons-httpclient-dev@jakarta.apache.org Received: (qmail 22658 invoked by uid 98); 27 Jan 2003 10:02:16 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Received: (qmail 22634 invoked from network); 27 Jan 2003 10:02:14 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 27 Jan 2003 10:02:14 -0000 Received: (qmail 35790 invoked by uid 500); 27 Jan 2003 10:00:36 -0000 Received: (qmail 35752 invoked from network); 27 Jan 2003 10:00:35 -0000 Received: from unknown (HELO nose.ch) (195.134.131.71) by daedalus.apache.org with SMTP; 27 Jan 2003 10:00:35 -0000 Received: (qmail 25614 invoked from network); 27 Jan 2003 11:00:47 -0000 Received: from calvin.nose.ch (HELO nose.ch) (192.168.1.7) by 0 with SMTP; 27 Jan 2003 11:00:47 -0000 Message-ID: <3E35034F.5020900@nose.ch> Date: Mon, 27 Jan 2003 11:00:47 +0100 From: =?ISO-8859-1?Q?Ortwin_Gl=FCck?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: de-ch, en-us MIME-Version: 1.0 To: Commons HttpClient Project Subject: Re: Configurable DNS resolver? References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Mike Moran wrote: > I'll look into it, but I investigated this a year or so ago and then > there was no way to replace the client side resolver. Regardless, one of > the main reasons I would do this would be to avoid synchronous lookups. > Even if the Java API was pluggable, it does not support asynchronous > lookups. Isn't JNDI supposed to be capable of looking up DNS names from a custom service provider?