Scheduled tasks #28

Closed
opened 2014-04-23 23:49:20 +00:00 by jamie · 2 comments
jamie commented 2014-04-23 23:49:20 +00:00 (Migrated from git.hazaar.io)

These will be like a cross between delayed functions and services. They will be set up like a service, except instead of running continuously they will be scheduled to run at a specified interval and/or time. We can probably take the CRON schedule format so that things will feel familiar.

This can be useful for things like batch processing tasks, such as daily email runs, or for the example I have in mind that instigated creating this feature, a process that reads data from various places and updates a database table cache at a specified interval.

Of course Warlock will be responsible for ensuring these tasks are triggered at the correct time and that they execute correctly. This will also mean that retries can be attempted using Warlocks failed execution retry function.

These will be like a cross between delayed functions and services. They will be set up like a service, except instead of running continuously they will be scheduled to run at a specified interval and/or time. We can probably take the CRON schedule format so that things will feel familiar. This can be useful for things like batch processing tasks, such as daily email runs, or for the example I have in mind that instigated creating this feature, a process that reads data from various places and updates a database table cache at a specified interval. Of course Warlock will be responsible for ensuring these tasks are triggered at the correct time and that they execute correctly. This will also mean that retries can be attempted using Warlocks failed execution retry function.
jamie commented 2014-10-15 01:11:31 +00:00 (Migrated from git.hazaar.io)

This has sort of been implemented in services. See #40 or the Services documentation for more information.

This has sort of been implemented in services. See #40 or the [Services documentation](http://www.hazaarmvc.com/docs/page/services) for more information.
jamie commented 2016-06-27 23:30:45 +00:00 (Migrated from git.hazaar.io)

Status changed to closed

Status changed to closed
Commenting is not possible because the repository is archived.
No milestone
No project
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: hazaar/hazaar-mvc-old#28
No description provided.