Skip to content
This repository has been archived by the owner on Sep 22, 2022. It is now read-only.

The ability to intentionally use write transactions from other (non-owner) threads. #200

Open
erthink opened this issue May 31, 2021 · 1 comment

Comments

@erthink
Copy link
Owner

erthink commented May 31, 2021

More flexible support of asynchronous runtimes/frameworks:

  1. Add an API-flag that explicitly allows use a write transaction from other threads, not only from which transaction was started.
  2. Add an API-function that returns a boolean value indicating that the IPC method used allows the lock to be released from another thread.
  3. Enhance the logic of checking the transaction owner thread:
    • when (1) is false: full restrictions (current behaviour), i.e. always check for the transaction owner;
    • when both (1) and (2) are true: no restrictions, i.e. no checking for the transaction owner;
    • otherwise when (1) is true, but (2) is false: a get/put functions without checking, but abort/commit still with full checking, i.e. a write transaction must be completed only by the thread that started it.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant