On 01/13/11 10:34 AM, Alan Bateman wrote:
Chris Hegarty wrote:
Are you referring to java.net.Proxy? Proxy.equals depends on the
resolution of its address. Address resolution could change over time,
depending on the caching policy. java.net.URL has a similar issue.
Just on this, are there issues with java.net.Proxy that should be added
to the javadoc? URL is a well known pariah but I didn't know about
java.net.Proxy. It looks like its equals depends on the equality of
socket addresses but that shouldn't involve lookups, right?
I think I may have jumped the gun here. I was thinking that unresolved
InetSocketAddresses would need to be resolved, but this doesn't appear
to be the case.
-Chris.
-Alan.
