Redis Pubsub about resque-status HOT 2 CLOSED

Hey mrduncan

the problem with pubsub + the ruby client is that unless you're using an event machine wrapper, you're still polling, just at a lower level. If you want to add some code to also publish statuses to an established key along side the existing way statuses are saved, that could be useful if you're subscribing to the statuses outside the ruby redis client.

from resque-status.

If you want to add some code to also publish statuses to an established key along side the existing way statuses are saved, that could be useful if you're subscribing to the statuses outside the ruby redis client.

You worded it much better than I did, but that's pretty much exactly what I was going for. Essentially resque-status would only publish messages about status changes. Any clients (EventMachine, node.js, etc.) would be responsible for subscribing to Redis to get the messages themselves.

from resque-status.