Re: Relieving some ClassLoader contention in PreferredClassProvider
Gregg Wonderly <[email protected]>
| Newsgroups | gmane.comp.java.sun.jini |
|---|---|
| Message-ID | <[email protected]> |
Bob Scheifler wrote: >> Yes, and I'd like to know as well, what specific behavior of equals or >> hashcode is being depended on > > I'm not sure what you're asking; codebase equality is defined to use > URL.equals, whatever that entails, not some particular piece. From an outside view, that's a fairly opaque description. I'm trying to understand whether it's intended to be that opaque or if there are a handful of known issues that URL.equals() covers which make up the required behavior. The DNS related details are perhaps part of the puzzle, but I'm just curious if you or Peter or someone else has any other specific, historical thoughts to clarify what might be at issue if an RMIClassLoaderSPI implementation used URL.toString().equals() instead of URL.toString(), besides the obvious address vs name considerations. Gregg Wonderly -------------------------------------------------------------------------- Getting Started: http://www.jini.org/wiki/Category:Getting_Started Community Web Site: http://jini.org jini-users Archive: http://archives.java.sun.com/archives/jini-users.html Unsubscribing: email "signoff JINI-USERS" to [email protected]