W3C home > Mailing lists > Public > whatwg@whatwg.org > November 2007

[whatwg] SQL API and database metadata at creation

From: Aaron Boodman <aa@google.com>
Date: Mon, 12 Nov 2007 10:29:22 -0800
Message-ID: <278fd46c0711121029s2f678955t9ed5b9b70349aff5@mail.gmail.com>
On 10/31/07, Ian Hickson <ian at hixie.ch> wrote:
> I agree, but like you I don't know exactly what to say about this. This is
> an area where implementation experience will help. It may be, for
> instance, that nobody uses more than one database per app, and a prompt
> ends up being fine.

I think one simple way to address this is to move the metadata into
the application itself. For example:

<html applicationName="Google Reader">

You can imagine other things eventually going in to this application
metadata, such as icons at various sizes.

I also think the estimated bytes thing is not that useful. It's going
to be hard for developers to estimate this and they're all just going
to but 64k or something they copied from an example.

I think it should be up to the UA to make sure that the database does
not grow "too large" and to prompt the user for access to more storage
when necessary on behalf of the application.

- a
Received on Monday, 12 November 2007 10:29:22 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:38 UTC