Re: Relieving some ClassLoader contention in PreferredClassProvider

> As URL.equals() is heavily used in the synchronized block from where the
> class loader creation takes place it means in the case that URL.equals
> takes a very long time all operation that ultimately result in the
> creation of a class loader are blocked.

So perhaps one should start by looking at alternate synchronization,
rather than alternate specification.

>> Do you have any actual practical demand for virtual hosting of codebases?
>
> Not at this time, but on the day you need it you don't have it.

Then I'm happy to wait for a day I suspect will never come.

>> And can you say what real problems result from the current semantics?
>
> the chance of conflicts with virtual hosting

I'm looking for you to expand on that. In particular, if all of the
URLs are HTTPMD:, what real problem can arise from equivalence?

> (and remember questions like this can't be answered reliably,
> given a largely silent user base ;-)

On the contrary, I'm asking you for what problems you see.
If you can't explain real problems, then I'm unmotivated to make a change.

> BTW Bob can you come up with an example of a URL that can't be
> recognized as a valid URI according to RFC 2396 and that might have been
> a workable codebase annotation, I tried to find an example but I couldn't.

new URL("http://foo[]bar.jar").toURI()

- Bob

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