The issue of custom DNS resolver has been discussed on several
occasions. The consensus was (if my memory does not fail me) that domain
name resolution was clearly out of HttpClient's scope. Instead we have
provided a way to plug in a custom DN resolution mechanism by supporting
virtual host names
Clemens,
Please see my comments below
On Fri, 2003-07-25 at 19:24, Clemens Marschner wrote:
> Hi,
>
> there are two issues I would like to bring up that were mentioned in this
> list during the last months but were never resolved:
>
> 1. Java DNS handling as done by java.net.Socket is very inef
Hi,
there are two issues I would like to bring up that were mentioned in this
list during the last months but were never resolved:
1. Java DNS handling as done by java.net.Socket is very inefficient for
applications that open connections to many different hosts.
This is due to a host name cache i
