remove event listiners from redis when connections end

Soves an issue where stopping and starting multiWorker child workers when passing in a redis connection directly would cause an event-emitter warning.

See #155 for more details.

v3.0.2: Check if setInterval().unref() exists before call

Test if unref() exists before calling it. This allows node-resque to work in a browser context (such as an electron render process).

• by @semiosis via #154

v3.0.1

Speed up the shutdown behavior of mutliWorker

v3.0.0

• Require that queue methods be async and require a callback
• Add actionhero's eslintrc, and make the code pretty
• Use the async library to dry up this project, enhance readability
• Block more than one task with the exact same args from being enqueuedAt (in) for at the same timestamp (to prevent non-deterministic behavior with locking plugins) (#145)

v2.1.2

(bug) worker domain errors should trigger after_perform

v2.1.1

(bug) worker.performInline needs result and error passed to worker for plugins

v2.1.0 worker#performInline

worker#performInline

DO NOT USE THIS IN PRODUCTION. In tests or special cases, you may want to process/work a job in-line. To do so, you can use worker.performInline(jobName, arguments, callback). If you are planning on running a job via #performInline, this worker should also not be started, nor should be using event emitters to monitor this worker. This method will also not write to redis at all, including logging errors, modify resque's stats, etc.

queue.locks and queue.delLock

Adds queue.locks() and queue.delLock() to help manage your resque locks.

v2.0.8

Fixes a memory leak in queue.stats

2.0.7: queue.stats

queue.stats() will let you inspect the resque stats of your cluster (failed, processed, etc)