W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2011

Re: Quota API to query/request quota for offline storages (e.g. IndexedDB, FileSystem)

From: Kinuko Yasuda <kinuko@chromium.org>
Date: Mon, 14 Feb 2011 20:37:16 +0900
Message-ID: <AANLkTim8NeencFWNEwVK-0Akx2eRgxgFQVL9L8KWsaJ8@mail.gmail.com>
To: Eric Uhrhane <ericu@google.com>
Cc: (wrong string) ‚‚ƒƒ•‚ƒƒƒ†‚) <ifette@google.com>
Thanks for all the feedbacks so far.

Now that the thread became quieter, I hope we're getting agreed,
at least on the basic concept.  To make the points clearer, let me
summarize what is being proposed (and what is not) with the quota API:

- To have unified, shared quotas between different storage APIs,
  except for localStorage.  (I'd include FileSystem API to the same group
  as other storage APIs.)
- To have a common distinction between temporary and persistent storages
  across different storage APIs.
- To have some sort of unified quota management system which can handle
  quota/usage query and request up front.  It is not mandatory to
  guarantee the requested quota though, and UA can return a quota error
  whenever it sees the actual or logical storage limit is reached.

As for the UI prompting, the proposing API specifies nothing about
the timing or frequency with which the prompting should be made,
except for a general guideline like:
- For persistent storage UA should properly communicate with the user
  about how much disk space should be used, and must not silently
  discard the user data without the user's permission.

I'm happy to hear more feedbacks if there are any.

Thanks,
Kinuko
Received on Monday, 14 February 2011 11:38:08 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:43 GMT