Intent to Ship: IndexedDB transaction explicit commit API call

[Victor Costan]

Contact emails pwn...@chromium.org,andrea...@google.com Explainer https://andreas-butler.github.io/idb-transaction-commit/EXPLAINER Spec https://github.com/w3c/IndexedDB/pull/242 Summary IDBTransaction objects will gain a commit() function that explicitly marks a transaction as not accepting further requests. Currently, IndexedDB only commits a transaction after all associated requests have had their completion event handlers executed, and no new requests have been queued by the event handlers. Developers can use the explicit commit() functionality to shave a few event loop cycles off of the latency of their transactions. Link to “Intent to Implement” blink-dev discussion https://groups.google.com/a/chromium.org/d/topic/blink-dev/ulyuFI9aMig/discussion Risks

Interoperability and Compatibility The feature was received positively by the other major browser vendors, and was added to the IndexedDB specification. It is very likely to become an interoperable part of the web platform. Firefox: Public support (https://github.com/w3c/IndexedDB/pull/242#issuecomment-401936151) Edge: Public support (https://github.com/w3c/IndexedDB/pull/242#issuecomment-428385752) Safari: Public support (https://github.com/w3c/IndexedDB/issues/234#issuecomment-391109023) Web developers: No signals Ergonomics Explicitly committing IndexedDB transactions commit() is expected to be used by applications that take advantage of the Page Lifecycle API: (https://developers.google.com/web/updates/2018/07/page-lifecycle-api#save-data-to-indexeddb-before-freezing). Developers who take advantage of this functionality will allow Chrome to release resources associated with IndexedDB transactions sooner. So, this feature will bring an improvement in performance and stability. Activation IndexedDB is generally wrapped in libraries, so this feature will be most impactful when adopted by the popular wrapper libraries. Libraries can use feature detection (check for IDBTransaction.prototype.commit) to take advantage of commit() today. Security This feature does not expose any new information, and does not introduce any new security risks.

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)? Yes Is this feature fully tested by web-platform-tests? Yes https://wpt.fyi/results/IndexedDB?label=master&product=chrome%5Bexperimental%5D&product=edge&product=firefox%5Bexperimental%5D&product=safari%5Bexperimental%5D&aligned&q=idb-explicit-commit Tracking bug https://crbug.com/898257 Link to entry on the Chrome Platform Status https://www.chromestatus.com/features/5375472036741120

[Victor Costan]

This feature has gone through a TAG review: https://github.com/w3ctag/design-reviews/issues/316

Apologies for the second email. chromestatus.com asked for a TAG review link, but didn't include it in the generated text that I emailed before. I filed an issue at https://github.com/GoogleChrome/chromium-dashboard/issues/643

Thank you for understanding,

    Victor

[Daniel Bratell]

LGTM1

(your intent is missing the TAG Review section where I think you should have said that it's not necessary to run this single method through that process)

/Daniel

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAP_mGKquFjG%2BZjgObG9nSKzcrWSaqimfz%3DJDmKddKCGV5k-3mg%40mail.gmail.com.

--

/* Opera Software, Linköping, Sweden: CET (UTC+1) */

[Daniel Bratell]

And who is silly now, I missed your second mail about tag. LGTM1 still stands.

/Daniel

[Chris Harrelson]

LGTM2

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/op.z02b5fp7rbppqq%40cicero2.linkoping.osa.

[Alex Russell]

LGTM3