(Dammit, forgot to reply-to-all. Sorry about the dup, mikeb!)<br><br>On 2 June 2011 06:40, Michael Bridgen <span dir="ltr"><<a href="mailto:mikeb@rabbitmq.com">mikeb@rabbitmq.com</a>></span> wrote:<br><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">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<br>
<a href="https://github.com/squaremo/rabbitmq-lvc-plugin" target="_blank">https://github.com/squaremo/rabbitmq-lvc-plugin</a>.<br></blockquote><div><br>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?<br>
<br>Tony<br></div></div>