Re: [Openjnlp-devel] Lazy jars

[Kevin H. <ke...@na...>]

On Wednesday, May 8, 2002, at 04:44 , Mario Cormier wrote:

> Kevin,
>
> First of all, the specification states that "a JNLP Client is always 
> allowed
> to eagerly download all resources if it chooses".  I think that as a
> default, you could use that instead of not doing anything with lazily
> downloadable resources.  At least things would work, and comply to the 
> spec
> too.
>
> Second, I reread this part of the specification and it still seems to me
> that my patch is a valid implementation as per the spec.  I agree with 
> you

I went back and carefully re-read the spec, I now agree with your 
interpretation. Caching is always optional. I don't want to treat lazy 
resources as eager because that could be a horrible performance issue at 
startup time. Your approach with directly accessing lazy resources via 
HTTP would be better. However, I have a better idea...

I've modified the classloader to cache lazy resources in a separate 
thread if any exist. This is done by the constructor, so lazy resources 
are cached right away but still allow the app to start running.

I modified findClass() to wait for lazy resources to be updated before 
failing on not finding a class. Only after all lazy resources are up to 
date and the class is not found will the ClassNotFoundException be 
thrown.