Skip to content
Spakman edited this page Sep 14, 2010 · 6 revisions

Probably rejected ideas – if you think I’m wrong, please tell me!

These would perhaps be better in something like jobby_rails.
  • 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.

From HHRy:

  • 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.

After 0.4 is released

  • 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!