This is the mail archive of the java-discuss@sourceware.cygnus.com mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: java.net: Classpath vs. libgcj Comparison

To: jsturm at sigma6 dot com
Subject: Re: java.net: Classpath vs. libgcj Comparison
From: Anthony Green <green at cygnus dot com>
Date: Sun, 16 Apr 2000 20:50:03 -0700
CC: per at bothner dot com, java-discuss at sourceware dot cygnus dot com, arenn at urbanophile dot com
References: <200004170142.SAA07217@hoser.cygnus.com> <m2vh1htq5q.fsf@kelso.bothner.com> <38FA829B.69CBA01F@sigma6.com>
Reply-to: green at cygnus dot com

Jeff wrote:
> Unless the classpath code somehow avoids these problems, I don't
> recommend caching address lookups.

Sun's "solution" was to add an implementation specific property,
sun.net.inetaddr.ttl, which you set to the number of seconds to cache
addresses for (or -1 for forever).

I looked this up in Sun's bug parade a while ago because I couldn't
believe they actually force implementations to cache in the spec.
Perhaps this was a mistake.

AG

-- 
Anthony Green                                                        Red Hat
                                                       Sunnyvale, California

Follow-Ups:
- Re: java.net: Classpath vs. libgcj Comparison
  - From: Jeff Sturm

References:
- java.net: Classpath vs. libgcj Comparison
  - From: Anthony Green
- Re: java.net: Classpath vs. libgcj Comparison
  - From: Per Bothner
- Re: java.net: Classpath vs. libgcj Comparison
  - From: Jeff Sturm

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]