Submitted by John O'Hara (not verified) on Wed, 2006/07/26 - 22:10.
IM and enterprise transaction messaging go after different spaces.
IM is all about presence, connectivity, innovative media. Enterprise messaging is about transactions, stability, reliabilty, determinism and some unusual topology requirements.
They're not the same. You would hate if I wanted XA support in XMPP :-)
As the chap behind AMQP (not Mr Davies, but first to leak always gets the credit, good for him :-), I can tell you this protocol has been under development for a long time. I looked everywhere for something that did this before being driven to do AMQP. That includes looking at XMPP, which is a lovely protocol, we use it here. But XMPP doesn't really want to do what AMQP does -- they are different with different underlying drivers as "Fearless soul" points out.
Also, note that AMQP is driven by both *users* and vendors and it is a genuinely open specification which all are free to implement (the license just looks complex).
Free software implementations of AMQP will be appearing soon. Look out for it and let us know what you think.
FYI: The "Advanced" part of AMQP is the exchange/binding/queue model, which few others have done so cleanly (but there are some passing similarities to SMTP). Other than that, it is meant to look simple.
AMQP and XMPP address different audiences, I hope the XMPP community do not see us as treading on their turf; that's not where we're going at all.
AMQP and XMPP; not competitors....
IM and enterprise transaction messaging go after different spaces.
IM is all about presence, connectivity, innovative media. Enterprise messaging is about transactions, stability, reliabilty, determinism and some unusual topology requirements.
They're not the same. You would hate if I wanted XA support in XMPP :-)
As the chap behind AMQP (not Mr Davies, but first to leak always gets the credit, good for him :-), I can tell you this protocol has been under development for a long time. I looked everywhere for something that did this before being driven to do AMQP. That includes looking at XMPP, which is a lovely protocol, we use it here. But XMPP doesn't really want to do what AMQP does -- they are different with different underlying drivers as "Fearless soul" points out.
Also, note that AMQP is driven by both *users* and vendors and it is a genuinely open specification which all are free to implement (the license just looks complex).
Free software implementations of AMQP will be appearing soon. Look out for it and let us know what you think.
FYI: The "Advanced" part of AMQP is the exchange/binding/queue model, which few others have done so cleanly (but there are some passing similarities to SMTP). Other than that, it is meant to look simple.
AMQP and XMPP address different audiences, I hope the XMPP community do not see us as treading on their turf; that's not where we're going at all.
Kind regards
John O'Hara
JPMorgan