technoweenie/coffee-resque — pull request #23 by mratzloff (2012-06-12 21:58:56+00:00)
Title: Fix #17, which allows resque-web to properly display workers

In reference to https://github.com/technoweenie/coffee-resque/issues/17

The problem is that when there is no work, or work is being completed too quickly, workers do not stay in the resque:workers set long enough to register in resque-web. You can see this with logging--workers are continuously being added and removed from the set. By removing the `track()` and `untrack()` calls in Worker, workers can now be monitored as expected. It also reduces the churn on Redis.

All tests pass, but I'm not sure if there was a specific reason it was handled this way.