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

Move lockMode into LockManager from ObjectProvider #224

Closed
andyjefferson opened this Issue May 28, 2017 · 0 comments

Comments

Projects
None yet
1 participant
@andyjefferson
Member

andyjefferson commented May 28, 2017

We can manage all locking requirements in the LockManager.

Also likely need to call clear() on the LockManager after a transaction has committed, since some locking requests are only for the current transaction.

We also should add convenience methods on the LockManager about whether a version should be updated for an object, and whether we should perform optimistic checks for an object.

andyjefferson added a commit that referenced this issue May 28, 2017

Migrate various methods into LockManager so that it starts to be more
like a centralised handler for locking/versioning. For #224

@andyjefferson andyjefferson added this to the 5.1.0.m3 milestone May 29, 2017

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