[rabbitmq-discuss] questions about rabbitmq

[Jeff C]

Hello all,

I recently began reading up on rabbitmq and the amqp paradigm, via rabbitmq's site documentation and miscellaneous tutorials around the web, as I plan to use rabbit as the core for a real-time forum component that will be part of a site I am working on, where new posts will be forwarded out to client machines from a long-polling/websocket server sitting between the users and rabbitmq.(I'm new to message passing systems) I've been reading some posts and even a talk from Alexis Richardson, and I decided to join the mailing list to ask some specific questions; I have three:


1. I've read that basic_consume is the most efficient way to receive messages from rabbitmq. Is it possible for one consumer (my websock/lp server) to register to multiple queues(conceivably several thousand) and have messages continually sent to it?

2. Also, what routing topology/architecture would you recommend for this use case? I was thinking about either one queue per user or, one queue per topic (which would only be created once someone actually visits said topic) where users reading the same topic would be subscribed to the same queue. Either way, all these queues would be forwarding messages to the websocket/comet server which would then push them out to clients. There would also be a work queue, pushing out tasks for crud operations in the database to worker machines.


3. I'm planning on using a non-blocking server (NIO, or maybe twisted) for pushing the messages, however, I'm not sure how I should go about the writes once a message is sent from rabbitmq. Iterating throught the set of ready connections to find the connection to send it through doesn't sound like the best way, and what if the connection is busy and isn't in the ready set of connections? What should be done with the message? 


Again I'm new to working with message passing systems as stated above, and a bit of help here would be much appreciated. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120203/44bac04b/attachment.htm>