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

Re: [IndexedDB] Granting storage quotas

From: Nikunj Mehta <nikunj@o-micron.com>
Date: Thu, 6 May 2010 01:36:56 -0700
Cc: Ian Hickson <ian@hixie.ch>, "Tab Atkins Jr." <jackalmage@gmail.com>, Jonas Sicking <jonas@sicking.cc>, Robin Berjon <robin@berjon.com>, public-webapps WG <public-webapps@w3.org>, Shawn Wilsher <sdwilsh@mozilla.com>
Message-Id: <DFF1124E-CC14-4DFD-BACC-D856EA7962E9@o-micron.com>
To: Dumitru Daniliuc <dumi@chromium.org>

I am not sure what the API expectations are for different levels of durability of storage APIs. Is it:

1. Options passed to individual APIs selecting durability level
2. Separate API calls for different durability level
3. Allocations occurring through markup requiring user actions which acts as ambient durability level for a site.

I surely would like to avoid 1 and 2. I felt like the discussion (based on your proposal) was leaning towards 3. However, I can't read this email in that way.

Thanks for clarifying for my sake.


On May 4, 2010, at 6:08 PM, Dumitru Daniliuc wrote:

> ian, it seems to me that nobody objects to adding a isPersistent optional parameter to openDatabase{Sync}() in the WebSQLDatabases spec (default = false). can you please add it to the spec? if isPersistent = true and the UA doesn't support persistent storage, then i believe openDatabase{Sync}() should throw a SECURITY_ERR just like it does when the DB cannot be opened.
> thanks,
> dumi
> On Thu, Apr 29, 2010 at 1:20 PM, Shawn Wilsher <sdwilsh@mozilla.com> wrote:
> On 4/29/2010 1:08 PM, Tab Atkins Jr. wrote:
> When you say "per site" do you mean per subdomain, or per domain?  The
> former is too permissive, the latter is too restrictive.
> I believe he means per origin.  At least that's what I took from our discussion.
> Cheers,
> Shawn
Received on Thursday, 6 May 2010 08:37:36 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:24 UTC