[w3c/IndexedDB] Durable database writes (#99)

We need a way to force data writes to disk to prevent loss of data in the event the app/database is "stopped". Firefox has implemented an experimental mode "readwriteflush" that can be used on a transaction such that when oncomplete event happens with success you can be sure that the data made it to the disk. This circumvents the "write cache" that has been implemented in Indexeddb and impacts performance, but for those of use that must ensure data is permanently stored this is a trade off we are willing to have.

As it stands. We have observed Edge Windows 10 1607 (OS level write caching turned off) IndexedDB can take 1 to 15+ minutes before committing a write to disk. We are testing with other systems (Android, IOS, etc) as well, but suspect the same behavior.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/IndexedDB/issues/99