Revert the changes to the error thrown.2014-01-06T13:47:15+00:00Simon MacMullensimon@rabbitmq.com2014-01-06T13:47:15+00:00193a68a100710a8faefbcb131ce413b3a2ce7083
small refactor: simplify AMQP version negotiation a little bit2014-01-01T19:36:35+00:00Matthias Radestockmatthias@rabbitmq.com2014-01-01T19:36:35+00:009a22fae75fa21d7424ba7c346bf7b0740a0ce213
correct typo in comment2014-01-01T19:26:30+00:00Matthias Radestockmatthias@rabbitmq.com2014-01-01T19:26:30+00:002e6a4b40e769cf6d73aae81dc975d480af585262
This was introduced in http://hg.rabbitmq.com/rabbitmq-server/rev/4852382b462b
This was introduced in http://hg.rabbitmq.com/rabbitmq-server/rev/4852382b462b
Keep the two handle_exception()s together.2013-12-19T12:10:21+00:00Simon MacMullensimon@rabbitmq.com2013-12-19T12:10:21+00:0098c71377de09f2183bce30aa780b1242f8955504
Treat connection errors on write the same as on read.2013-12-17T15:42:06+00:00Simon MacMullensimon@rabbitmq.com2013-12-17T15:42:06+00:006c8e13f5d57f5ebac9937ca9110823bbe71d3368
Make sure that our last event before going sorta-idle is not one in which we claim to be in flow control.2013-12-05T18:23:11+00:00Simon MacMullensimon@rabbitmq.com2013-12-05T18:23:11+00:00549a9ca6b3da26d68e13bcfdb628039b5e0b2117