[Webkit-unassigned] [Bug 22700] ApplicationCache should have size limit

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=22700





------- Comment #5 from michaeln at google.com  2009-04-28 15:40 PDT -------
Some drive-by comments and questions...

* What happens if a cacheGroup that is in the act of being updated gets
evicted? Maybe those not be subject to eviction?

* What precautions prevent the particular cache group that is being updated (or
added to) and causing the need to evict something from being evicted itself?

* The eviction logic examines 'caches' and decides which to boot, maybe this
should look at 'cacheGroups' instead.

* I'm not sure if a partially updated caches are left around (after the network
connection drops midway thru) and the update picks up where it left off upon
the next attempt. If so, these partial updates could be the first to go without
having to blow away the associated group altogether.

* Maybe the decision making about which cacheGroups to evict should be left to
a delegate api provided by the embedding browser? The system currently has no
way of determining which groups are more or less important (outside of LRU). I
could see that being value added by host browsers.


-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.