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: Mon, 19 Apr 2010 22:08:17 -0700
Message-ID: <s2o5dd9e5c51004192208zaca3707fkbd3fe95a4d20baff@mail.gmail.com>
To: Shawn Wilsher <sdwilsh@mozilla.com>
Cc: Joćo Eiras <joaoe@opera.com>, Mark Seaborn <mseaborn@chromium.org>, public-webapps@w3.org
On Mon, Apr 19, 2010 at 9:13 PM, Shawn Wilsher <sdwilsh@mozilla.com> wrote:

>  On 4/13/2010 8:53 AM, Joćo Eiras wrote:
>> Not really. The user agent can ask for quota from the user when the limit
>> is being hit without the webpage even having to worry about it. Opera 10.50
>> does that.
> I agree with this, and do see the benefit of adding more to the spec.

Sure.  That addresses item 1 of Mark's original question, but what about

On Tue, Apr 13, 2010 at 3:09 AM, Mark Seaborn <mseaborn@chromium.org> wrote:

>  2) It is too permissive because it enforces no limit on the amount of
> space a web app can use:  A web app from example.com can create an
> unlimited number of puppet subdomains:  aaa.example.com, bbb.example.com,
> etc.  It can use aaa.example.com's 5Mb allocation by loading a script
> from aaa.example.com in an iframe and communicating with it using
> postMessage().

As far as I'm aware, no one (including Chromium) has a solution to at the
moment.  Which probably should be a cause for concern.  :-)
Received on Tuesday, 20 April 2010 05:09:07 UTC

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