- From: Victor Costan <notifications@github.com>
- Date: Tue, 09 Oct 2018 16:01:45 -0700
- To: w3c/IndexedDB <IndexedDB@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 9 October 2018 23:02:07 UTC
@aliams My understanding of this feature is that it lets sites hint to the implementation that they're done with the transaction. It's intended to enable optimizations, not to be a new capability. A malicious site can still cause a lot of disk writes by opening up many transactions and letting them auto-commit. Committing is still asynchronous, so the implementation has the opportunity to rate-limit and/or batch transactions. Does this help reason about abuse potential for the new API? -- 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/pull/242#issuecomment-428382130
Received on Tuesday, 9 October 2018 23:02:07 UTC