[rabbitmq-discuss] STOMP instalation on Ubuntu

m.luchak at smartasking.com m.luchak at smartasking.com
Fri Apr 20 12:42:46 BST 2012

Hi Matthias,
I apoligize as I had forgotten about this thread.  Thanks for the input.  This requirement of receiving messages previously published to an exchange was discarted... We were (are, hehe)  very green with AMQP and RabbitMQ and we didn't have a clear grasp of exchanges, queues etc..
We made a simple tweak to the sequence of when bindings are created to implement AMQP "the right way" and we no longer have clients who are missing messages.
-----Original Message-----
From: "Matthias Radestock" <matthias at rabbitmq.com>
Sent: Friday, April 20, 2012 6:22am
To: m.luchak at smartasking.com
Cc: rabbitmq-discuss at lists.rabbitmq.com
Subject: Re: [rabbitmq-discuss] STOMP instalation on Ubuntu


On 16/04/12 16:38, m.luchak at smartasking.com wrote:
> On my other question; Does anyone have insight as to the "right way" to
> implement the following:
> A consumer comes online and subscribes to a topic exchange after
> messages have been published. This consumer must receive the prior messages.

Can you explain in more detail what behaviour you are looking for? On 
the surface it would appear to require a broker to remember messages 
indefinitely. I.e. unless the broker has prior knowledge of all 
consumers, it has no way of knowing when it is safe to discard a message 
since another consumer may come along in, say, a year's time, subscribe 
to the topic, and expect to receive all prior messages.

> I understand that using STOMP is one way to acheive this, but is it the
> only way?

Rabbit's stomp plug-in uses AMQP under the covers. So whatever it 
accomplishes certainly can also be achieved with AMQP.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120420/a3ea6059/attachment.htm>

More information about the rabbitmq-discuss mailing list