-
Notifications
You must be signed in to change notification settings - Fork 2
TODO for 0.4
Spakman edited this page Sep 14, 2010
·
6 revisions
- Add a tasty Ruby interface for adding jobs from within Ruby. Damn the COW?
- Use Syslog rather than the Ruby Logger – I’ve no idea why I haven’t thought of this before it makes much more sense. Thanks to John Leach for pointing this out at the Scottish Ruby Conference 2010.
- Ability to specify niceness of the children forked from a jobbyd.
- Fix the known bugs.
- Ensure I’m not creating a race condition with #close_on_exec = true. See:
- Job priority – it was always intended to be handled by different jobbyd processes (I prefer the flexibility of that).
- Retrying of jobs has been mentioned – I think that is a better job for the jobby client/child to handle than be coped with in the daemon.
- To tie in with the 0.4 release, I’d like to replace jobby_rails with ‘jobby_rack’, a much nicer and lighter way to deal with job queues
- I’d also like to see jobby it’s self managing it’s sate – probably with something clever like Tokyo Cabinet. That should make it easier to pass actual marshalled procs to Jobby too, since we can write arbitrary blobs.
- Promote this project properly! I’ve not yet found anything that does what this does – tell me if you know of something that does, please!