[ ] simplify current implementation, no need to extend event emitter
[ ] support full configuration of webhooks, alternate urls, fallback urls, monitoring, etc.
[ ] allow customization of endpoint requests. This should allow people to post on queues, etc. Support Amazon SQS and Azure Storage Queue. Support HTTP Basic Auth for outbount links
[ ] [nice to have] make it api-compatible with azure scheduler
[ ] maintain a job history, store the results for all the executed jobs
[ ] [nice to have] add a ui for the scheduler-drone in angular.js
[ ] find a way to bundle recurring jobs toghether, so they don't appear as being separated from each other
[ ] syntax for a scheduler job, what it contains and how it translates to work docs: retry policy, http verb&url, what to do when there is an error, recurrance params, time of day, job state, outbound endpoint response, etc.
Old and busted todos
use redis as a backend and especially it'sEXPIRE NOTIFY
featurerest api and programatic api (only when embedded in node.js applications)complete refactor, rewrite everything in coffeescript, use express.js for rest api, use mocha for testing