-- to be continued --
[FEATURE] Add Locking API
This patch adds a flexible locking API, which allows to be
extended by extensions.
It also deprecates the old API and adjusts all Core usages.
Reviewed-by: Helmut Hummel <firstname.lastname@example.org>
Tested-by: Helmut Hummel <email@example.com>
Reviewed-by: Alexander Opitz <firstname.lastname@example.org>
Tested-by: Alexander Opitz <email@example.com>
[FOLLOWUP][TASK] Add meaningful exceptions to new locking API
This adds dedicated exceptions to the new locking API which
vastly simplifies usage workflows.
Since the new API was not yet released, this is a non-breaking
Reviewed-by: Markus Klein <firstname.lastname@example.org>
Tested-by: Markus Klein <email@example.com>
Reviewed-by: Jigal van Hemert <firstname.lastname@example.org>
Tested-by: Jigal van Hemert <email@example.com>
#4 Updated by Ernesto Baschny over 6 years ago
- Category changed from Code Cleanup to Backend API
Will work continue on this front? Is there a concept plan or some documentation on the end goal of this refactoring?
This is more than a "Code Cleanup", it introduces a new Locking API. So it should aim to replace the current "Locker" class. So missing still is:
1) a "flock" locking mechanism
2) make it used by the Core, making sure the old "Locker" class is not used anymore
3) deprecate the Locker class
Is it realistic that we reach the goal of finishing this API before feature freeze (which would be next week but will most probably be postponed) and that we reach the goal of "replacing the usage of Locker" before the final release?
#6 Updated by Christian Kuhn about 5 years ago
- Status changed from Under Review to Rejected
While the work on this is highly appreciated and the pending patch was a good step into the right direction, it was pending as WIP in gerrit for a year now without anyone really working on it. The patch was abandoned for the time being. Meanwhile, a blueprint for locking evolved at http://wiki.typo3.org/Blueprints/LockingForCaches and the work here is mentioned there for anyone to pick up.
This issue here will be set to "rejected" for now, since further works needs to be aligned and decided in the blueprint, and after that realized in smaller and new issues.