On 5/31/11, Felix Halim wrote:
> On Mon, May 30, 2011 at 10:39 PM, Bjartur Thorlacius
> wrote:
>
> The dynamic resources only updated if the user visit the particular
> app cached web-page.
>
Yeah, that's logical. Caches should still be allowed to refetch
resources just before they're expected to
On Mon, May 30, 2011 at 10:39 PM, Bjartur Thorlacius
wrote:
> The following is how I understand your requirements; please correct me where
> correction is due.
> You've got two types of resources:
>
> 1. static resources, to be retrieved once and cached indefinitely
> 2. dynamic resources, to be
Þann mán 30.maí 2011 03:42, skrifaði Felix Halim:
Hmm.. yes, I think "unlimited" is a bad word (I just use it because
currently App Cache quota is unlimited).
Let me explain my need for pageStorage in a different way:
Suppose I have a web page and want to store it in an App Cache. This
web page
Hmm.. yes, I think "unlimited" is a bad word (I just use it because
currently App Cache quota is unlimited).
Let me explain my need for pageStorage in a different way:
Suppose I have a web page and want to store it in an App Cache. This
web page requires a few resources (.ccs, .js, images, etc..)
On 5/28/11, Felix Halim wrote:
> To summarize, the pageStorage offers "unlimited" storage for dynamic
> content for the App Cached web pages.
User agents may store expired pages for offline use. Internet Explorer
and Firefox have 'Work offline' modes automatically enabled on
complete disconnection
AFAIK, currently there is no storage limit for the App Cache.
However, localStorage does has limit of 5 MB.
It is silly to force the user to "install" a web page just to get
unlimited localStorage.
I'm thinking why not introduce an "unlimited pageStorage" that behaves
like App Cache?
The pageStora