TYPO3 Core

I took a closer look at the execution pool that each task possesses as a member variable. It is meant to be an array of task executions. I guess the original thinking was that there could be several executions (i.e. with different start times, end times, type (single run/recurring) and frequencies) for a given task class, and that all those executions would be stored in the same DB record. I guess it would have meant there would only ever be a single record per task class.

This is not the way it is currently implemented in the BE module. There's no way to add more than one execution in the execution pool. And I think this is just as well, as it would make it very complicated to manage in the BE interface. It's better to have a separate database record for each execution type/frequency/etc. of a given class.

This would mean that the execution pool doesn't need to be an array. Changing this would be a rather important change and maybe it's a bit late to do it. OTOH the Scheduler is still not committed to Core and it would be the right moment to still change that.

Opinions? Please.