Nathan Esquenazi

Better support for testing jobs

12

From @bradgessler: A stub could be provided for peeps that want to assert jobs are thrown on the queue in a test env. Make testing a job is performed work...

Create a threaded worker

3

Would be cool to create a threaded worker for processing beanstalk jobs possibly using [celluloid](https://github.com/celluloid/celluloid) similar to @mperham's [sidekiq](https://github.com/mperham/sidekiq) or just a custom threaded solution.

Discussing with @bradgessler: Currently: ``` ruby Backburner::Worker.enqueue NewsletterSender, [self.id, user.id], :ttr => 1000 ``` instead: ``` ruby Backburner::Worker.enqueue Backburner::Job.new(NewsletterSender, [self.id, user.id], :ttr => 1000) ``` or: ``` ruby # include...

From #52, need to support priority labels in configure block

Allow ResqueCompat module to support old resque 1.1 users

``` ruby beanstalkd://localhost/foo?retry_times=5 # parse prefix and retry from the url ```

Tube namespacing to support versioning? in the wiki

From @bradgessler: CLI for querying/filtering jobs for performing batch operations on jobs that are in the queue. This is important for when things go bad in production and certain jobs...

From @bradgessler: > I don't think having different queues per app is a good idea in a beanstalkd world. Resque does this because there's no concept of priorities in Redis....

Cleanup github pages and add logo. As suggested by @bradgessler we can use http://thenounproject.com/noun/stove/#icon-No4325 as a starting point.  Download the SVG and PNG here: https://www.dropbox.com/s/kndb4kv5py4m5nh/stove.zip