Re: Relieving some ClassLoader contention in PreferredClassProvider

Bob Scheifler wrote:
>> Up to this point has something passed by from which I should be able to
>> *really* conclude that from within the Jini team people are extremely
>> reserved for such a change.
>
> I'm speaking only for myself.

That explains a lot ;-)

So I will rephrase "Up to this point has something passed by from which
I should be able to *really* conclude that you are extremely reserved
for such a change?"

I'm not trying to be a smart ass and maybe I didn't read carefully but I
find it very hard to directly find wording that you think that indeed
URL.equals and hashCode() has its problems but that you are very anxious
to change the behavior because of ...

So if you are extremely reserved for such a change is that for other
reasons than the fact some people might rely on this exact behavior of
URL.equals()
--
Mark

--------------------------------------------------------------------------
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]