Re: [w3c/IndexedDB] Configurable task priority for IDBRequest and IDBTransaction? (Issue #428) from Evan Stade on 2024-10-11 (public-webapps-github@w3.org from October 2024)

From: Evan Stade <notifications@github.com>
Date: Fri, 11 Oct 2024 12:37:29 -0700
To: w3c/IndexedDB <IndexedDB@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/IndexedDB/issues/428/2408018779@github.com>

My first inclination would be to be able to set this on the level of the entire IDB database. It will be easier to implement and reason about that way. Also because transactions block each other, so it's not particularly useful to be able to add a high priority transaction behind a low priority one. 

And from an API perspective, I would suggest adding it via Storage Buckets. IDB is probably not the only storage API that could benefit from this, and one of the main advantages of Storage Buckets is to not have to update N APIs every time a generally useful dial, such as this one, is added.

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

Message ID: <w3c/IndexedDB/issues/428/2408018779@github.com>

Received on Friday, 11 October 2024 19:37:33 UTC