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

Re: [IndexedDB] Granting storage quotas

From: Jeremy Orlow <jorlow@chromium.org>
Date: Wed, 21 Apr 2010 14:00:11 -0700
Message-ID: <k2m5dd9e5c51004211400w4858c161j34b19ace56f3eed4@mail.gmail.com>
To: Michael Nordman <michaeln@google.com>
Cc: Mike Clement <mikec@google.com>, public-webapps@w3.org
On Wed, Apr 21, 2010 at 1:03 PM, Michael Nordman <michaeln@google.com>wrote:

>
>
> On Wed, Apr 21, 2010 at 12:10 PM, Mike Clement <mikec@google.com> wrote:
>
>> FWIW, the "transient" vs. "permanent" storage support is exactly why I
>> eagerly await an implementation of EricU's Filesystem API.  Being able to
>> guarantee that the UA will not discard potentially irreplaceable data is of
>> paramount importance to web apps that want to work in an offline mode.
>>
>> I also find that the current arbitrary quota limit of 5MB per domain makes
>> local storage APIs unusable for all but the most rudimentary apps (e.g.,
>> sticky note demo apps).  There is an asymmetric distribution of local
>> storage needs out there that no one is yet addressing (e.g., a photo- or
>> video-related app might need GBs of local storage, an offline mail app might
>> need tens or hundreds of MB, a TODO list app might only need kilobytes,
>> etc.).
>>
> I wholeheartedly support any effort to coordinate quota management among
>> all of the various local storage APIs.  The issue of quota limits is
>> something that browser vendors will need to address soon enough, and it's
>> probably best left up to them.  The need for "permanent" storage across all
>> local storage APIs, though, is something that in my opinion should come out
>> of the standardization process.
>>
>
> Here's a stab at defining programming interfaces that make a distinction
> between "transient" vs "permanent" for the storage mechanisms. If we make
> additions like this, we should use the same terminology across the board.
>
> // WebSqlDBs, also could work for IndexedDBs
> window.openDatabase(...);   // temporary
> window.openPermanentDatabase(...);
>
> // AppCaches, embellish the first line of the manifest file
> CACHE MANIFEST
> CACHE MANIFEST PERMANENT
>
> // FileSystem, see the draft, i've change the terms a little here
> window.requestFilesystem(...);    // evictable
> window.requestPermanentFilesystem(...)
>
> // LocalStorage
> window.localStorage;    // purgeable
> window.permanentLocalStorage;
>

I think Tab's right that permanent space should only be initiated based on
user gesture, not by some JS API.
Received on Wednesday, 21 April 2010 21:01:02 GMT

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