<div dir="ltr"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">> How does QoS manage to load-balance multiple queues within a channel?<br>
> I thought the queue consulted the limiter before delivering a new<br>
> message...in that case could one add a little bit of logic to the<br>
> limiter to prefer one queue over another? I believe there is already<br>
> some logic in the limiter that tracks rejection rates per<br>
> queue...could this be implemented as an extension to that?<br>
<br>
Not really, it's "one phase commit" -- the queue says "will you take<br>
this message?" and the limiter either commits and gets the message, or<br>
doesn't and is thereafter considered blocked. �Thus there's no<br>
opportunity to defer acceptance.<br>
<br>
Prioritising consumers for a queue would be easier I think, but sadly<br>
that is the one permutation that no-one seems to need.<br>
<br>
-Michael<br></blockquote><div><br></div><div>Can one create a Prioritised "topic exchange"?</div><div>msg1 topic= 0.0.0.1 #first</div><div>msg2 topic= 0.0.0.3 #4th</div><div>msg3 topic= 0.0.0.2 #2nd</div><div>msg4 topic= 0.0.0.4 #3rd</div>
<div><br></div><div>�</div></div></div>