You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"I think all IDB open requests (for an origin) are put into one queue, and are processed in order. So while there is a blocked open request for version X+1, any new requests for version X will be blocked as well and won't result in new connections (and will eventually fail with an error when the X+1 completes)"
I found it difficult to find this behavior in the spec and assumed that I would have to figure out some kind of dining-philosophers solution to prevent requests from starving each other. A little non-normative webdev-facing text might help. @inexorabletash
The text was updated successfully, but these errors were encountered:
"I think all IDB open requests (for an origin) are put into one queue, and are processed in order. So while there is a blocked open request for version X+1, any new requests for version X will be blocked as well and won't result in new connections (and will eventually fail with an error when the X+1 completes)"
I found it difficult to find this behavior in the spec and assumed that I would have to figure out some kind of dining-philosophers solution to prevent requests from starving each other. A little non-normative webdev-facing text might help. @inexorabletash
The text was updated successfully, but these errors were encountered: