- From: Bevis Tseng <notifications@github.com>
- Date: Sun, 20 Aug 2017 19:56:32 -0700
- To: w3c/IndexedDB <IndexedDB@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 21 August 2017 02:56:53 UTC
I'd prefer proposal#2. Regarding "queue a task" in #1 , I think this IDBRequest is very special and is different from all the other IDBRequest which could only be blocked by other requests bound to a specific IDBDatabase connection. Hence, it is reasonable that, in an implementation, there are multiple queues and each one is only bound to an IDBDatabase connection. However, for this getDatabase IDBRequest, it's an request in per-origin scope instead of per IDBDatabase which breaks this assumption. Hence, "queue a task" is not clear enough for this case. We should at least ensure that there is no version change transaction blocking while running this getDatabase operation, don't we? -- 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/31#issuecomment-323635338
Received on Monday, 21 August 2017 02:56:53 UTC