Just an idea that came to mind:
In order to give the developers more control over the recurring tasks, we may move all definitions of recurring tasks into a file bundled with each new project created.
This allows developers to change the frequency of tasks, or disable them.

For example, reposearch uses a mechanism that manages the reindexation of autocomplete suggestions when needed. WebDSL has this recurring task built-in, invoking it every 12 hours (and thus also on app initialization). This task is resource intensive for reposearch, and I would like to disable the built in recurring tasks for this reason.

If we decide to isolate the recurring task definitions into an editable file scheduledTasks.app, we might need to add a check during compilation, such that we can warn developers of existing applications that scheduledTasks.app is missing. Or better: generate scheduledTasks.app if it is missing.

Asked by Elmer van Chastelet on 15 February 2013 at 10:53


Answered by Elmer van Chastelet on 15 February 2013 at 10:53