Feature #3938
closed
Use t3lib_syslock instead of serialzed_executions
0%
Description
Check if it's possible to use the built-in TYPO3 lock mechanism instead of keeping a serialized list of executions in the database. The thing is that this list is not used just for avoiding multiple executions, but also for checking on old scripts which should be cleaned up.
Both features must still be possible with t3lib_syslock.
Updated by Christian Kuhn about 13 years ago
- Status changed from New to Rejected
- Priority changed from Could have to Won't have this time
Rejected:
t3lib_lock can not be used because it is only for one php run and can not be used to lock things between different accesses.
There is the table sys_lockedrecords with an API in t3lib_befunc, but the API does not provide a way to fetch all locked records, delete one of them and things like that.
I'd say that the current solution is fine for now, we could refactor if at some point in the future a generic locking API that fits our needs evolves. In this case we should open a new issue.
Updated by Francois Suter about 13 years ago
Fine. Thanks for the explanations. I had never looked in detail.
Updated by Michael Stucki almost 11 years ago
- Project changed from 739 to TYPO3 Core
- Category changed from scheduler to scheduler