Hi Michael.<br><br><div class="gmail_quote">On Fri, Mar 18, 2011 at 13:31, Michael Bridgen <span dir="ltr"><<a href="mailto:mikeb@rabbitmq.com">mikeb@rabbitmq.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Right, at the minute the last values are transient. It probably wouldn't take much coding to make it save things to disk for durable exchanges.<br></blockquote><div><br></div><div>OK, that figures... :) I know nothing of Erlang, but I'll take an overall look and try to come up with an acceptable solution for my case. Would that be a feature useful enough that you'd consider including in your code?</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
It will work with any queue. However, if you have many consumers to a queue, each message will be delivered to one consumer only -- that's the semantics of AMQP queues. �So, in your case, I think you want a queue for each consumer anyway.</blockquote>
<div><br></div><div>Sorry for not being clearer, that's what I meant by 'exclusive' queues, not the exclusive on AMQP terminology.</div><div>Thank you.</div></div>