W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2012

[QUOTA] Misleading example in Quota handling in storage API section

From: Tobie Langel <tobie@fb.com>
Date: Fri, 8 Jun 2012 22:07:26 +0000
To: "public-webapps@w3.org" <public-webapps@w3.org>
Message-ID: <CBF8443A.8972D%tobie@fb.com>

In section 5 of the Quota Management API ("Quota handling in storage
API")[1], the last sentence of the first bullet point reads:

    "For example, Application Cache may silently discard or fail to cache
data when it is hitting quota limit."

This is actually incorrect, AppCache is atomic and hitting the quota limit
would trigger a cache failure as per step 17.5 of the application cache
download process[2].

    "If the user agent is not able to store the resource (e.g. because of
quota restrictions),
    the user agent may prompt the user or try to resolve the problem in
some other manner
    (e.g. automatically pruning content in other caches). If the problem
cannot be resolved,
    the user agent must run the cache failure steps."

In turn, this would fire an error event and bust the cache.

Best to pick another example.


Received on Friday, 8 June 2012 22:07:52 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:34 UTC