<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">2013/7/2 Steve Valaitis <span dir="ltr"><<a href="mailto:steve@digitalnothing.com" target="_blank">steve@digitalnothing.com</a>></span><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div id=":1h2" style="overflow:hidden">So the<br>
queue.bind command is what's causing the ^amq\.gen-.* write permission<br>
to be required? </div></blockquote><div><br></div><div>Either queue.bind or queue.declare without passive = true.</div><div><br></div><div>With Bunny 0.9, it should be pretty clear what line causes the authorization exception.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div id=":1h2" style="overflow:hidden">
<br>
What if I had a durable queue that multiple processes were connecting<br>
to. With that scenario wouldn't anyone connecting to that queue also<br>
be able to publish new messages to it?</div></blockquote></div><br>You can have a durable shared queue with multiple consumers.<br><div><br></div><div>Here is an example of a read-only consumer connection. Note that in order to avoid declaring</div>
<div>the queue, you just get a reference to it with :passive => true:</div><div><br></div><div><a href="https://github.com/ruby-amqp/bunny/commit/ea05c4eba9a063615e41bd0cb126abbe04ded91f">https://github.com/ruby-amqp/bunny/commit/ea05c4eba9a063615e41bd0cb126abbe04ded91f</a></div>
-- <br>MK<br><br><a href="http://github.com/michaelklishin" target="_blank">http://github.com/michaelklishin</a><br><a href="http://twitter.com/michaelklishin" target="_blank">http://twitter.com/michaelklishin</a><br>
</div></div>