<div dir="ltr"><div>Hi Ben and Alexis,</div>
<div> </div>
<div>Thank you very much for your helpful reply. </div>
<div> </div>
<div>What I am planning to do is to have C clients publishing some events ( as text message ) to RabbitMQ and on the other side, I would have Jave clients that need to listen on the messages. </div>
<div> </div>
<div>The tricky part is that I need something in between Java clients and RabbitMQ to do the brokering based on an ID. For example, the C clients will associate each event with an ID. Each Java client may listen to events of one or more IDs. I am not sure if I can program that brokering rule within RabbitMQ or I need a singleton client to listen on all messages coming out of RabbitMQ and then do the brokering to the end-clients. </div>
<div> </div>
<div>Any suggestion will be greatly appreciated.</div>
<div> </div>
<div>Thanks alot for all your help.</div>
<div> </div>
<div>Best Regards,</div>
<div>Pete</div>
<div><br><br> </div>
<div class="gmail_quote">On Sun, Aug 24, 2008 at 12:05 AM, Alexis Richardson <span dir="ltr"><<a href="mailto:alexis.richardson@cohesiveft.com">alexis.richardson@cohesiveft.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div class="Ih2E3d">Pete<br><br>On Sat, Aug 23, 2008 at 12:31 PM, Pete Kay <<a href="mailto:petedao@gmail.com">petedao@gmail.com</a>> wrote:<br>><br></div>
<div class="Ih2E3d">> I have a series of load-balanced clustered servers and they all publish<br>> events in the form of text messages. I am looking for using RabbitMQ to<br>> listen on event messages from all the clustered servers and then publish it<br>
> out to subscribed clients.<br>><br>> Is this something that RabbitMQ good at doing?<br><br></div>Absolutely - yes.<br><br>RabbitMQ has a model based on queues, which buffer (and optionally<br>persist) messages on behalf of subscribers. So when you publish a<br>
message to a RabbitMQ broker, it will be placed on one or more queues<br>based on really simple filtering rules:<br><br>- In the simplest case you can copy a message to *every* queue in the<br>broker. This is called 'fan out'.<br>
- Or, you can give each message a 'routing key', and then the broker<br>will use this key to determine which queues to place the message on<br>- You can also enable richer routing patterns<br><br>We're here to help so please can you tell us a bit more about what<br>
kind of 'subscribed clients' you plan to use. Also - what language<br>are you writing your code in? There are plenty of clients but it<br>would be good to know which one you wish to use.<br>
<div class="Ih2E3d"><br><br><br>> I am new to RabbitMQ. Any suggestion will be greatly appreciated.<br><br></div>There is some documentation here: <a href="http://www.rabbitmq.com/documentation.html" target="_blank">http://www.rabbitmq.com/documentation.html</a><br>
<br>Here is an introduction that may help:<br><a href="http://www.slideshare.net/somic/introduction-to-amqp-messaging-with-rabbitmq/" target="_blank">http://www.slideshare.net/somic/introduction-to-amqp-messaging-with-rabbitmq/</a><br>
<br>alexis<br><br><br>><br>> Best Regards,<br>> Pete<br>><br>><br>> _______________________________________________<br>> rabbitmq-discuss mailing list<br>> <a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
> <a href="http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>><br>><br></blockquote></div><br></div>