- From: Joshua Bell <notifications@github.com>
- Date: Thu, 31 Mar 2016 09:22:55 -0700
- To: whatwg/storage <storage@noreply.github.com>
Received on Thursday, 31 March 2016 16:23:25 UTC
IMHO, the easiest thing as far as IDB is concerned is to force-close all the connections, which is what Chrome does if the user manually deletes data. That's what @mikewest has in the header-based approach spec (on my recommendation, I think...). That prevents any new operations from starting (as above), but also terminates any in flight (so yes, need state). Agreed with @jakearchibald that this also also seems necessary in the "sd card removed" scenario where we can't pretend the data is still there but will go away after all handles are closed, and I don't think we want to have two different models. Which means I think I agree with the direction this is trending. Also, @mikewest was looking forward to hooks in Storage for his header to talk to, so hopefully he's seeing these pings... --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/storage/issues/4#issuecomment-204007270
Received on Thursday, 31 March 2016 16:23:25 UTC