[RFC][PATCH][icedtea-web]: Added support for signed JNLP file- Updated Patch

[Omair Majid]

On 07/25/2011 01:49 PM, Saad Mohammad wrote:
> On 07/25/2011 01:14 PM, Deepak Bhole wrote:
>> I thought we had this discussion on IRC before.. I may be mistaken, but
>> didn't we determine that there should never be a case where caching is
>> not possible? If so, I think aborting here would be the right thing to
>> do..
>>

Oh, yes, I recall that now. In that case, Saad, please ignore my comment.

> Yes, we did have this talk. We talked about using the 'cache' attribute
> within jar element. eg:
> <jar href='myResource.jar' main='true' cache='no' />
>
> Not really sure if the cache attribute really exist, I couldn't find any
> documentation on it. :P

Sorry, but I cant recall this bit at all :/ I dont think I have ever 
seen that cache attribute. The JARDesc class in IcedTea-Web has an 
attribute cacheable, but that's only used by the plugin.

> But anyways, I think Omair is talking about the 'download' attribute. eg:
> <jar href='myResource.jar' main='true' download='lazy' />
>

Well, yes and no. Jars being cached is orthogonal to jars being 
downloaded lazily.

> If the cache attribute exist, do both behave similarly? It's always cached?

Lazy just refers to when a jar is downloaded (and it has to be 
downloaded so the java class files can be read and the code executed - 
whether it's being cached or not), not if it is kept on disk.

Cheers,
Omair