No misunderstandings... When the AMQP working group was founded, RHAT took a very assertive role over AMQP and created versions that no-one else implemented, and which were pushed through the working group by sheer political force. Read the abomination that is the AMQP/0.9 spec, if you have the courage. The determination of RHAT to create incompatible forks of the spec is a large part of what killed AMQP in our eyes. We spent several years trying to save AMQP from that. We failed. We're a small team, RHAT had 20 people working on this.

> We're a small team, RHAT had 20 people working on this.

They should have realized they already failed when they allocated 20 people just do work on the protocol specification. This is another example of a design by committee done by a large enterprise vendor and how it results in a a bloated, inefficient and overly complicated specification.

All 20 people feel the need to justify their time by adding more crap and features to the design. Usually no matter how simple or complicated the actual protocol needs to be, its specification will always be proportional to the number of people * time assigned to work on it.

Ah, another one bites the dust by the hands of an "enterprise" software vendor. These guys make money selling free software to big companies that are too stupid to realize that their support contract is about as valuable as the paper it's written on.