-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Convert synchronized usages to AutoLock #5083
Comments
* Replaced relevant usages of synchronized with AutoLock. * Made AutoLock serializable since classes that use it may be stored in the HttpSession. * Added convenience methods to AutoLock to execute lambdas with the lock held. * Introduced AutoLock.WithCondition to use a Lock and a Condition together. Signed-off-by: Simone Bordet <[email protected]>
This issue is under the Loom umbrella issue #5078. |
But this change needs to stand on it's own merits rather than be justified by Loom. |
@gregw this change has already improved locking in few places, clarified others and spun off #5081 and #5086. Overall it is a good cleanup, but obviously getting rid of all |
Updates after review. Signed-off-by: Simone Bordet <[email protected]>
Updates after review. Signed-off-by: Simone Bordet <[email protected]>
…ed_to_autolock Fixes #5083 - Convert synchronized usages to AutoLock.
Fixes after merge. Signed-off-by: Simone Bordet <[email protected]>
Jetty version
10.0.x
Description
To be more Loom friendly we need the usages of
synchronized
to be converted to usejava.util.locks.Lock
or, better, Jetty'sAutoLock
.This would allow early testing of Loom prototypes on a more fair basis.
The text was updated successfully, but these errors were encountered: