<div><font face="arial, sans-serif">If you don't use RabbitMQ with Ruby, feel free to skip this</font></div><div><font face="arial, sans-serif">thread entirely.</font></div><span style="font-family:arial,sans-serif;font-size:13px"><div>
<span style="font-family:arial,sans-serif;font-size:13px"><br></span></div>I am thinking about changing return values in the high level API</span><div style="font-family:arial,sans-serif;font-size:13px">in Bunny 0.9 to support method chaining like amqp gem does:</div>
<div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px"><a href="https://gist.github.com/80f9acec43255c5c7b29" target="_blank">https://gist.github.com/80f9acec43255c5c7b29</a></div>
<div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px"><div>Currently B::Queue#bind returns an instance of the response</div><div>(AMQ::Protocol::BindOk), for many operations those methods</div>
<div>are not particularly useful.</div><div><br></div><div>Is it a better idea to support method chaining? Folks who need</div><div>access to responses can always use Bunny::Channel#queue_bind</div><div>and other "low-level" methods on B::Channel.</div>
<div><br></div><div>What do you think?</div></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>
<br>