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: green at cygnus dot com
- Subject: Re: java.net: Classpath vs. libgcj Comparison
- From: Per Bothner <per at bothner dot com>
- Date: 16 Apr 2000 19:30:41 -0700
- Cc: java-discuss at sourceware dot cygnus dot com, arenn at urbanophile dot com
- References: <200004170142.SAA07217@hoser.cygnus.com>
Anthony Green <green@cygnus.com> writes:
> java.net.InetAddress Really liked the caching mechanism of the classpath implementation, this classpath class seems very strong, and is preferable
> to the libgcj version.
Is having java.net.InetAddress do caching really a good idea? It
seems to me that if caching is a good idea (which it is), doing it in
the Java library is the wrong place, since there is a good chance it
duplicates a cache in the C library, in the kernel, or the local name
server. If none if these actually do caching (which would surprise
me), then that is an suggestion that caching is not worthwhile.
--
--Per Bothner
per@bothner.com http://www.bothner.com/~per/