On Wed, Sep 22, 2010 at 12:51 AM, Aaron Bentley <[email protected]> wrote: > I have been assuming that dispatching tasks (e.g. Jobs, Builds) was the > primary use case for RabbitMQ. You say we have a separate need for > passing messages between components. Can you give me examples of ways > you'd like to use RabbitMQ that aren't related to tasks?
Here are a few things I have lined up that could be done via rabbit: -Send oops reports to lp-oops immediately rather than later. -Trigger completion of long-poll paused requests on appservers. -raise traps when things like the queue retry limit trigger The long poll stuff is arguable just the end-point of tasks being run in the NewTaskSystem, but many things won't need that, so I think its worth considering it as a related but separate concern. -Rob _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
