<br><div class="gmail_quote">On Mon, May 9, 2011 at 1:02 PM, Michael Klishin <span dir="ltr"><<a href="mailto:michael.s.klishin@gmail.com">michael.s.klishin@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Gavin,<br>
<br>
I see that pika is callbacks-oriented. If so, maybe it can do what amqp gem does: it actually runs an errback when possible authentication failure is detected, but also provides a default callback that raises an exception. This way library user can choose between the two and failure to define the errback is visible. Just a suggestion.<br>
</blockquote><div><br></div><div>Thanks, that sounds like a good solution. The main issue right now is we don't start tracking state for callbacks until after the connection is negotiated and do so based upon frames. It should be trivial to add the right kind of errback prior to connection.open-ok, I just want to make sure I implement it correctly where it comes across as a kludgy after-thought.</div>
<div><br>Gavin</div></div>