[RFC][Icedtea-web]: Changed how cache works.

[Denis Lila]

Hi again.

My previous e-mail was mostly just low level implementation
comments. I have only one problem with the design:
right now our cache management metadata is stored in RecentlyUsed
which is a <leastRecentModification, fileName> map. Storing
information about the time of last update of a cached
resource using the time as a key seems very unnatural to me.

Right now, CacheLRUPolicy.cacheOrder isn't really a hash map
at all. It's just a list of <time, name> couples because
every time we read from it we start out with the name and try
to read the time. In other words, given the value we try to
read the key. That is very backwards for a hash map, which
is supposed to provide the value given the key.

If we could somehow make the resource that we're caching the
key and the time of last update the value, I think that would
simplify things a lot. In particular we might be able to
entirely get rid of these identifiers that we're adding to
folder names and times. And also checking whether something
is in the cache and updating it should be made much simpler
(no loops would be required).

What do you think?

Regards,
Denis.

----- Original Message -----
> Hi Andrew.
> 
> I've been looking over this. Rather than saying what I
> don't like, I committed your patch to a local repository
> and changed whatever I didn't like. It's much easier to
...