[RFC][Icedtea-Web]: Enforce cache limit based on deployment.properties
dbhole at redhat.com
Mon Mar 21 13:08:30 PDT 2011
* Andrew Su <asu at redhat.com> [2011-03-21 15:50]:
> We can not remove old files because we don't know if they are in use.
Why not address this problem first? Make it so that we can determine if
files are in use? We already use a lock file to determine if other
instances of netx are running when clearing cache. Can't it be extended to
share-lock the downloaded files?
> The way I see to fix this is to do it on the -last- jvm shutdown for plugin/javaws. Where it will have to find out which file is new and save those by going through all the files.
> I'm just not happy about having to go through every file.
> > >
> > > TBH, I wouldn't even want overwrite any files while plugin/javaws is
> > > running.
> > >
> > Exactly. We know that JVM can behave in all sorts of weird ways if
> > jars
> > that it's using are modified.
More information about the distro-pkg-dev