InetAddress should utilize networkaddress.cache.ttl for getLocalHost() too (original) (raw)
Alan Bateman Alan.Bateman at oracle.com
Wed Jul 11 00:00:04 PDT 2012
- Previous message: InetAddress should utilize networkaddress.cache.ttl for getLocalHost() too
- Next message: InetAddress should utilize networkaddress.cache.ttl for getLocalHost() too
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 05/07/2012 07:10, Deven You wrote:
Hi All,
I noticed that InetAddress.getLocalHost() uses cache to improve the performance. However the default implementation is caching local host within 5 seconds. From the spec, networkaddress.cache.ttl should be used to control the cache behaviour and I think it is a better solution. For example, if the networkaddress.cache.ttl is set to -1 which means always cache the local host then we can avoid unnecessary operations on getAddressesFromNameService to improve the performance. I have made a patch for this solution, so anyone would like to take a look? [1] http://cr.openjdk.java.net/~littlee/OJDK-527/webrev.00/ <http://cr.openjdk.java.net/%7Elittlee/OJDK-527/webrev.00/> Thanks a lot! -- Best Regards, Deven I'm not sure about this one as I suspect it will cause problems in DHCP or any environments where the host addresses changes, say moving to a different wireless network or waking up a machine after hibernation.
-Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.openjdk.java.net/pipermail/net-dev/attachments/20120711/f547ae51/attachment.html
- Previous message: InetAddress should utilize networkaddress.cache.ttl for getLocalHost() too
- Next message: InetAddress should utilize networkaddress.cache.ttl for getLocalHost() too
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]