crowdtap/promiscuous — pull request #3 by nviennot (2012-10-06 20:33:09+00:00)
Title: Promiscuous::Worker -> Promiscuous::Subscriber::Worker

Code changes:
1) Trapping signals is done in the rake task which now both start and
stop the reactor.
2) unit_of_work has been extracted since all workers should use it.

Concerns:
Do we need a mutex around the mongo update when replicating
subscribers ?
It wouldn't be surprising that we keep pumping messages while mongo
blocks on the socket.
If Mongoid uses a poll of connections, we most likely need to
serialize. Note that If we do, we just need it during save!

Maybe we could offer different levels of consistency, because
some of our users may already be resilient to reading out of order
writes.