[rabbitmq-discuss] How to handle full exchange history delivery

Tony Garnock-Jones tonygarnockjones+rabbitmq at gmail.com
Thu Jun 2 17:43:01 BST 2011

(Dammit, forgot to reply-to-all. Sorry about the dup, mikeb!)

On 2 June 2011 06:40, Michael Bridgen <mikeb at rabbitmq.com> wrote:

> By way of illustration: the last-value-caching exchange, though it was
> developed as a verification of the exchange type mechanism, is rather
> awkward; in the main because it is encoded in the existing AMQP operations
> (bind, consume), and these aren't the right vocabulary for the intended use.
>  See the "Limitations" section of
> https://github.com/squaremo/rabbitmq-lvc-plugin.

Aren't these RabbitMQ implementation restrictions rather than things that,
in principle, require new or different AMQP vocabulary? If new vocabulary
really is required, what kind of thing do you have in mind?

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

More information about the rabbitmq-discuss mailing list