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

Eliminate beginExclusive()/endExclusive() #4

Open
climategadgets opened this issue Sep 21, 2021 · 0 comments
Open

Eliminate beginExclusive()/endExclusive() #4

climategadgets opened this issue Sep 21, 2021 · 0 comments
Labels
legacy Issues related to bit rot - there's been a lot of it since 2000 stability

Comments

@climategadgets
Copy link
Member

Background

Decision to use beginExclusive()/endExclusive() for locking comes from times before Java code existed. It was not quite applicable even when the library was in active development (early 2000s), and today it is completely obsolete; it makes the application fragile and prone to deadlocks.

Task Definition

As an Application Architect, I want to change the design so that the need to use beginExclusive()/endExclusive() pair is gone.

Acceptance Criteria

The library can be used exactly the way it is used today without beginExclusive()/endExclusive() being used.

@climategadgets climategadgets added legacy Issues related to bit rot - there's been a lot of it since 2000 stability labels Sep 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
legacy Issues related to bit rot - there's been a lot of it since 2000 stability
Projects
None yet
Development

No branches or pull requests

1 participant