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: Fri, 23 Apr 2010 11:17:14 -0700
Message-ID: <s2r5dd9e5c51004231117s3ad87993x1e71e8a2e2e7ac62@mail.gmail.com>
To: Shawn Wilsher <sdwilsh@mozilla.com>
Cc: Nikunj Mehta <nikunj@o-micron.com>, Michael Nordman <michaeln@google.com>, Mike Clement <mikec@google.com>, public-webapps@w3.org
On Fri, Apr 23, 2010 at 11:08 AM, Shawn Wilsher <sdwilsh@mozilla.com> wrote:

>  On 4/23/2010 7:39 AM, Nikunj Mehta wrote:
>> Could we create an additional optional parameter for an open request with
>> the type of permanence required? Or is it not a good idea?
> I haven't talked to anyone at Mozilla that thinks that having permanent and
> non-permanent-but-possibly-long-lasting data to be a good idea.  There does
> seem to be support for a session-only version of indexedDB.

What then do people at Mozilla propose for use cases like flickr/picasa
wanting to cache files on the hard disk iff there's plenty of space to do
so, but making sure that said caches are not a burden if that users hard
disk later fills up?

Received on Friday, 23 April 2010 18:18:04 UTC

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