java.net: Classpath vs. libgcj Comparison

Sun Apr 16 19:33:00 GMT 2000

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/