While iMatix was the original designer of AMQP and has invested hugely
in that protocol, we believe it is fundamentally flawed, and
unfixable. It is too complex and the barriers to participation are
massive. We do not believe that it's in the best interest of our
customers and users to invest further in AMQP. Specifically, iMatix
will be stepping out of the AMQP workgroup and will not be supporting
AMQP/1.0 when that emerges, if it ever emerges.
By the way, the AMQP spec is roughly the same size as the HTTP spec, and the latter spends a lot of pages listing just status codes.
And of course, AMQP uses a model based on Sessions, which is great if the components of the system are static, but not that great if you're talking to a lot of nodes who come and go, since you'll end up with uneven load distribution on your servers.
Regardless of HTTP as a particular implementation, I think statelessness makes perfect sense in a unreliable network of nodes.
