- From: David Grogan <dgrogan@chromium.org>
- Date: Fri, 14 Jun 2013 15:37:25 -0700
- To: Kyle Huey <me@kylehuey.com>
- Cc: "public-webapps@w3.org" <public-webapps@w3.org>
Received on Friday, 14 June 2013 22:38:12 UTC
Filed https://www.w3.org/Bugs/Public/show_bug.cgi?id=22370 to track this. On Thu, May 9, 2013 at 6:01 PM, Kyle Huey <me@kylehuey.com> wrote: > On Thu, May 9, 2013 at 4:09 PM, David Grogan <dgrogan@chromium.org> wrote: > >> On Thu, May 9, 2013 at 4:01 PM, David Grogan <dgrogan@chromium.org>wrote: >> >>> jsbell pointed out an annoyance with this approach. If we delete the >>> entire backing store while opening a database, we can alert the page that >>> that particular database was lost via the mechanism discussed in this >>> thread. >>> >> >> To clarify, chromium stores all databases for an origin in a single >> leveldb instance, so this is a real possibility for us. >> > > Yeah, I fear that giving anything remotely specific gets too far into > implementation-detail land. > > - Kyle >
Received on Friday, 14 June 2013 22:38:12 UTC