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

[whatwg] Asynchronous database API feedback

From: Scott Hess <shess@google.com>
Date: Tue, 11 Dec 2007 12:08:39 -0800
Message-ID: <696e4b7c0712111208j6daf5f07l64617615719e2ffb@mail.gmail.com>
On Dec 11, 2007 11:22 AM, Aaron Boodman <aa at google.com> wrote:
> Or does
> globalStorage not guarantee that data is written when the setter
> returns?

A thing I've been thinking about for Gears would be the ability to
spin up an in-memory/async "session" database, with the sense of
"session" being the same as for "session cookie".  For this database,
when control returns from an update statement, the data is _not_
guaranteed to be on disk, and if your browser crashes it is explicitly
guaranteed to be gone.  So far, so useless, except if you allowed the
system to attach that database to a persistent database.  In such a
system, you could do synchronous operations against the session
database, and bulk async operations to propagate the data to the
persistent database.

Received on Tuesday, 11 December 2007 12:08:39 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:59 UTC