[rabbitmq-discuss] Help defining appropriate queue model

yoav glazner yoavglazner at gmail.com
Wed Mar 2 21:35:59 GMT 2011

On Wed, Mar 2, 2011 at 7:24 PM, Fabio Margarido <fabiomargarido at gmail.com>wrote:

> On Wed, Mar 2, 2011 at 14:12, Alexis Richardson <alexis at rabbitmq.com>
> wrote:
> >> Or failing that, perhaps a bit like the "real time record" model, such
> as used for financial data, where a consumer gets the last published update
> for a topic. IIRC the guys at Rabbit HQ did some work on an exchange which
> persists the last update to a topic - what became of that? This would fit
> the problem definition quite well, I think.

you can make one queue named - conifg_data
and always call basic_reject() on new config messages (with newer versions
or such...)
on old config messages call basic_ack and they will be gone...

don't forget to make the queue durable and the messages persistent if that
is needed.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20110302/e38f1b9d/attachment.htm>

More information about the rabbitmq-discuss mailing list