W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2011

Re: [IndexedDB] setVersion blocked on uncollected garbage IDBDatabases

From: Jeremy Orlow <jorlow@chromium.org>
Date: Tue, 8 Feb 2011 15:43:00 -0800
Message-ID: <AANLkTi=PxatUq3KYLx0C+8uj27WD7O5YghP4E5CmCC0R@mail.gmail.com>
To: Glenn Maynard <glenn@zewt.org>
Cc: ben turner <bent.mozilla@gmail.com>, Jonas Sicking <jonas@sicking.cc>, Joćo Eiras <joao.eiras@gmail.com>, public-webapps <public-webapps@w3.org>
On Tue, Feb 8, 2011 at 3:31 PM, Glenn Maynard <glenn@zewt.org> wrote:

> On Tue, Feb 8, 2011 at 4:01 PM, Jeremy Orlow <jorlow@chromium.org> wrote:
>
>> I talked it over with Darin (Fisher), and he largely agreed with you guys.
>>  I'll file a bug saying that after unload, all IDBDatabases attached to that
>> document should be closed.
>
>
> What happens if a database is open in a page in the back-forward cache?
> That's incompatible with onunload having side-effects.
>
> I know the BF-cache is off-spec, but it's extremely useful and will
> hopefully find its way into the standard some day, so it'd be nice to keep
> it in mind.
>

As long as the behavior as far as developers can tell matches the spec, you
can do just about whatever you'd like behind the scenes.


> I suppose the browser would discard whole pages from the BF-cache on demand
> if required by a setVersion call.
>

That sounds like it'd more or less work.

J
Received on Tuesday, 8 February 2011 23:43:50 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:43 GMT