"What is AMQP and should I be interested in it?"

re: "What is AMQP and should I be interested in it?"

Hans — Mon, 30 Nov 2009 00:24:36 GMT

And one tiny detail that really rocks the casbah: since the Mono project finally got an implementation of the System.Messaging namespace that is based on AMQP (e.g. with RabbitMQ), one could dream of applications that talk to each other e.g. from Windows to Mac OSX - using exactly the same .NET code base!

If this only came true... [[[sigh]]]

re: "What is AMQP and should I be interested in it?"

JohnBrea — Mon, 30 Nov 2009 11:38:46 GMT

That's an interesting point.

I see that earlier this year (2009), Microsoft put the ECMA 334 (C# Language Specification) and ECMA 335 (Common Language Infrastructure) specifications under their Community Promise.

Will have to wait and see what comes up.

Cheers

John Breakwell (MSFT)

re: "What is AMQP and should I be interested in it?"

JohnBrea — Wed, 09 Dec 2009 12:45:10 GMT

Hi Hans,

I passed your comment to my colleagues in the product group and they provided some feedback:

"Microsoft’s implementation of System.Messaging uses MSMQ underneath and is not going to be able to talk to any program which doesn’t use MSMQ. The transport is not selectable like it is with WCF.

If somebody ports that chunk of Mono to Windows, and RabbitMQ as well, then it could work. Unfortunately, the AMQP implementation which Microsoft is participating in is Qpid, not RabbitMQ. There is no standard native client API for AMQP, so whatever Mono is doing to interface with RabbitMQ isn’t going to work with Qpid."

Reference for Microsoft and Qpid:

http://port25.technet.com/archive/2008/11/07/finally-dive-into-the-deep-participation.aspx

Cheers

John Breakwell (MSFT)