Hi,
I was recently looking at
https://bugs.webkit.org/show_bug.cgi?id=22700
I have a small patch that attempts to fix this issue by
1. allowing the ChromeClient implementers to decide what the size
limit should be,
2. evicting caches (in LRU order) from the database when the size
limit is
The way I see it, there's 2 uses for AppCache in the mobile space:
Simply speeding things up (i.e. just a cache) and web applications you'd
like to use offline. For the first use case, automatic eviction (presumably
via LRU) is quite acceptable. For the second use case, I think you need
some way
The chrome team had an interesting thread on this topic not long ago.
Unfortunately it wasn't on the public chromium-dev mailing list, so I
can't provide a link to it here :(
summary (according to me at least:)
The gist of it was that providing appcaching for general use w/o any
special
Good point. Tying the apps together is pretty important. What good is it
for the program to still be in AppCache if it's data (in databases or
localStorage) was deleted by some other LRU policy?
I'm not sure that yet another manifest is needed though. For databases and
localStorage, access is
On Wed, May 6, 2009 at 12:45 PM, Jeremy Orlow jor...@google.com wrote:
Good point. Tying the apps together is pretty important. What good is it
for the program to still be in AppCache if it's data (in databases or
localStorage) was deleted by some other LRU policy?
I'm not sure that yet
On Wed, May 6, 2009 at 1:12 PM, Michael Nordman micha...@google.com wrote:
On Wed, May 6, 2009 at 12:45 PM, Jeremy Orlow jor...@google.com wrote:
Good point. Tying the apps together is pretty important. What good is
it
for the program to still be in AppCache if it's data (in databases or
06.05.2009, в 23:09, Michael Nordman написал(а):
There is no means for the system to distinguish between these two
cases. There is no API to indicate which use is which.
The first use case (just speeding things up) sounds like something
that should be handled by a normal HTTP cache, as
2009/5/6 Alexey Proskuryakov a...@webkit.org
06.05.2009, в 23:09, Michael Nordman написал(а):
There is no means for the system to distinguish between these two
cases. There is no API to indicate which use is which.
The first use case (just speeding things up) sounds like something that
On May 6, 2009, at 11:40 AM, Jeremy Orlow wrote:
The way I see it, there's 2 uses for AppCache in the mobile space:
Simply speeding things up (i.e. just a cache) and web applications
you'd like to use offline. For the first use case, automatic
eviction (presumably via LRU) is quite
9 matches
Mail list logo
