netzooid

The title says it all - why hasn’t SOAP/XMPP taken off? SOAP over HTTP is gross. Status codes, soap actions, and the inherent synchronocity of it make SOAP over HTTP suck. (For example consider this document with every possible mapping for WS-Addressing and HTTP)

XMPP has a specification (unlike JMS ;-)). It also has a big public infrastructure. And there are a lot of libraries out there on which to build upon. So why hasn’t it taken off?

I can think of a few reasons:

• Unfamiliarity - we aren’t comfortable with XMPP yet
• Latency - XMPP does introduces intermediaries, but I have no idea if this is actually an issue or not.
• Lack of support and documentation - For instance, XFire has XMPP support, but almost no documentation for it.

Thoughts?

This entry was posted on Thursday, March 2nd, 2006 at 4:54 pm and is filed under Random.