Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support transaction timeouts #43

Closed
inexorabletash opened this issue Oct 7, 2015 · 2 comments
Closed

Support transaction timeouts #43

inexorabletash opened this issue Oct 7, 2015 · 2 comments

Comments

@inexorabletash
Copy link
Member

Two cases;

  • abort a transaction if it hasn't been able to start before the timeout (e.g. other transactions are holding the lock)
  • abort a transaction if it hasn't attempted to commit before the timeout (i.e. this transaction is too busy)

Chrome does the second automagically in the case of a hung renderer.

Imported from https://www.w3.org/2008/webapps/wiki/IndexedDatabaseFeatures

@kristofdegrave
Copy link

In the first case I would use a blocked callback like when you want to open a newer version of the database and have existing connections. This way you give the developer control on how he wants to act on this

@inexorabletash
Copy link
Member Author

TPAC 2019 Web Apps Indexed DB triage notes:

We think this can be done in user-space, either with just timeouts and abort calls, and/or some of the proposals over in #34

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants