Hacker News new | past | comments | ask | show | jobs | submit login
Gartner:XMPP future standard for real time communication (process-one.net)
15 points by BuddhaSource on Dec 23, 2010 | hide | past | favorite | 15 comments



This is a press release with no evidence cited about XMPP's takeover. They do say there is some evidence in two linked documents, but both are behind pay walls. Where's the meat?


Gartner's business model: sell enterprise-friendly papers on the latest industry buzzwords; drive sales by sending hollow press releases to clueless business/IT journalists.


Gartner's business model is something along the lines of "make a prediction about tech $flavour-of-the-month to insecure CTOs with a timespan of about three years. Three years later, things have moved on and everyone has forgotten their prediction." Whether right or wrong.

Apparently you pay good money for these predictions.


If XMPP doesn't take over, then something embodying its good ideas will. That seems obvious to me. What form the eventuality will take seems up for grabs, though. Why Gartner would proclaim anyone the winner so soon is anyone's guess.


Twitter uses XMPP and now even diaspora is also looking into to adopting XMPP.

Again may not be enough to call it 'the meat' :P


LOL, but even those two points aren't mentioned in the article.

I'm down to talk about XMPP; I share your interest in the subject. I just don't know why anyone voted this particular submission up.

Sorry, I don't mean to be an HN curmudgeon.


It would nice if it would have been more specific about google's usage (for IM) or facebook's usage at all.

Although facebook still sucks at it (no tls support yet even)


How does Twitter use XMPP?


Yea sorry, but word on the street is that Twitter replaced XMPP with streaming HTTP connections because they found that XMPP doesn't scale. Something about the fact that a slow XMPP client can bring down the whole server because of messages backing up.

Allegedly Google Chat ditched XMPP too. Behind the scenes it's some proprietary system that is somehow compatible with XMPP for 3rd party clients.

Also, not to be a dick, but I don't think the founders of Diaspora are an authority on scalable realtime data.


Twitter had an XMPP gateway to send tweets. They were never built on XMPP.

Google still uses XMPP. On Android phones this isn't exposed as a service to other apps (if you want that, use Rene Treffer's excellent https://github.com/rtreffer/AsmackService).

Android's XMPP bits use a proprietary binary protocol to communicate with their XMPP server farm. Probably to reduce power consumption. You can still use any 3rd party XMPP client to connect into google's XMPP cloud.


What this guy said!


Gartner is pay to play research.


Is there a non-xml "flavor" of xmpp? Doesn't seem like an xml protocol is the wave of the future based on current trends.


XMPP is known for real time but poor to scale. I have my doubts on this, but could somebody suggest any alternatives?


So perhaps a badly written individual server doesn't scale (neither does an individual Apache instance).

Google manages to scale XMPP to support each of their Gmail users. Is that big enough?

Nokia runs all of the Ovi account on a Tigase-based backend. That's quite a few users.

And all these disperate networks federate into a massive <cough>"web-scale"</cough> cloud of XMPP federation.

So as someone building massively scaled components on XMPP, it scales!




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: