Where Is the Real-Time Web Message Bus?

Looking at my Google Alerts this morning I saw this one;

So after quick read at of this article on ReadWriteWeb I posted the following as a comment.

I'll declare a vested interest in XMPP first, our service Cleartext ESM (Enterprise Social Messaging) uses XMPP.

Now I'll also say that it's worth noting that XMPP does enterprise and internet scale and is good at bridging these through an ecosystem of components, I think this is a key benefit.

There's a third issue with Twitter in addition to business model and latency at large scale (which I don't believe you can solve with http polling) and that is shifting technology road map. For anyone to build complicated enterprise and internet level apps on Twitter this needs to be solved and as the platform is evolving rapidly that's a big ask.

For example parts of our platform rely on the fact that re-tweets and hash tags are in the message. Twitters recent news that RT's will become part of the API is good news for short messages but bad news for solutions proxying Twitter if only because we all have to do more R&D, which equates to delays to market and increased costs.

I'm firmly believe that email succeeded because its an open, standards based, federated platform. XMPP delivers the same for IM and mirco-blogging. I think this is the real time bus you're looking for.