This is the mail archive of the
java-discuss@sourceware.cygnus.com
mailing list for the Java project.
Re: java.net: Classpath vs. libgcj Comparison
- To: mdw at cs dot berkeley dot edu
- Subject: Re: java.net: Classpath vs. libgcj Comparison
- From: Andrew Haley <aph at pasanda dot cygnus dot co dot uk>
- Date: 17 Apr 2000 07:58:11 -0000
- CC: bryce at albatross dot co dot nz, arenn at urbanophile dot com, classpath at gnu dot org, gs at sevenmountains dot no, java-discuss at sourceware dot cygnus dot com
> From: Matt Welsh <mdw@cs.berkeley.edu>
> Date: Sun, 16 Apr 2000 22:13:22 -0700
>
> Bryce McKinlay <bryce@albatross.co.nz> writes:
> > I disagree with this. Caching inside InetAddress is a misfeature. The underly
> > ing OS already caches DNS entries.
>
> Really? Do *all* underlying O/S's cache Internet address lookups?
No, they don't. Recently I tracked down a problem with an overloaded
name server to a room full of machines running a rival OS. :-) Each
machine was doing several identical DNS lookups every second!
> My guess was that this was added to java.net.InetAddress to mask any
> incompatibilities between operating systems in this regard.
That's possibly true, but that doesn't excuse an incorrect
implementation; a cache that doesn't obey the expiration times is
wrong.
Andrew.