On Wed, Apr 1, 2015, at 05:12 PM, Andrew Sutherland wrote: > On Wed, Apr 1, 2015, at 03:02 PM, ben turner (bent) wrote: > > If a crash or power loss occurs at just > > the right moment then the transaction will be lost/rolled back. It should > > still be impossible to ever see database corruption though. This will > > mean faster delivery of "complete" events, and more closely aligns with > > the performance vs. stability tradeoffs other browser vendors have > > chosen. > > Can you clarify the risk profile a little more? Specifically:
And I forgot one other thing: - Wake lock interaction. Could there be a problem if an application drops its wake-lock in the oncomplete notification for the transaction? (Or does IndexedDB hold a wake-lock to cover this and/or the kernel take care to flush dirty pages to disk before suspending/etc.?) Andrew _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
