Actions
Feature #3938
closed
Use t3lib_syslock instead of serialzed_executions
Status:
Rejected
Priority:
Won't have this time
Assignee:
-
Category:
scheduler
Target version:
-
Start date:
2009-07-17
Due date:
% Done:
0%
Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:
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 
Updated by 
Updated by
Actions