[10.x] Refactor hardcoded lock/wait for integers #48818
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an alternative solution to #48795 which was closed with the reason:
Contrary to this statement, it cannot be defined on route groups, only individual routes. Regardless of that, I think it's in the best interests of the framework to not hard code values. Developers can now easily override the default
locksForandwaitsForvalues without having to rewrite the entirehandleRequestWhileBlocking()method.