jmettraux/rufus-scheduler — Issue #31: Refactor: simplify at/in/every by quickly handing them off to cron
Author: d11wtq
Created: 2012-03-01 01:43:04+00:00
State: open

It seems like the at/in/every jobs can all be represented as cron jobs. For example:

every 5s => */5 * * * * *
in 30m => 0 30 0 1 3 2012 (assuming midnight 29th Feb 2012 when created)

"at" is obviously compatible.

Just a thought anyway :) I'm dissecting the code to look at adding support for distributed scheduled jobs, across multiple machines, without worrying about the scheduler running in multiple locations (backed into redis).