[rabbitmq-discuss] New AMQP 0-9-1 extension added in default/master

[Michael Klishin]

I'm happy to report that RabbitMQ 3.2 will support a new AMQP 0-9-1
extension that makes it possible for clients to be notified about
blocked connections [1].

Documentation for the extension is available on next.rabbitmq.com [2].
It is currently supported by 4 clients (in their development branches):

 * Java client
 * .NET client
 * Erlang client
 * Bunny (http://rubybunny.info)

with a couple more clients working on supporting it in the near future.

If you maintain a RabbitMQ client, below are some notes about how
you can add support for this extension.

We've introduced two new AMQP 0-9-1 methods: connection.blocked
and connection.unblocked. This codegen commit demonstrates what
properties of what types they have:
http://hg.rabbitmq.com/rabbitmq-codegen/rev/1748e6cf399a

Next, you need to add connection.blocked to the list of supported extensions
in client capabilities.

How these methods are exposed in the API is client-specific. 
3 clients (Java, .NET, Bunny) let users register event handlers (callbacks)
on connection instances.

Below are two diffs that may help you add support for connection.blocked
to your client:

http://hg.rabbitmq.com/rabbitmq-java-client/rev/fc3a59ca0aab
https://github.com/ruby-amqp/bunny/commit/334d0ceb3f84c03be342ad06dd244f0aa25fb7bc

To test this functionality you can either build RabbitMQ from source (on the default branch)
or use nightly builds available from https://www.rabbitmq.com/nightly-builds.html

If you have any questions about this extension, simply reply to this thread.

1. http://www.rabbitmq.com/memory.html
2. http://next.rabbitmq.com/connection-blocked.html
--
MK

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130807/c8ed3a1c/attachment.pgp>