Linked by Thom Holwerda on Sat 25th May 2013 00:45 UTC
Google "So in summary... Google has pulled the plug on support on a protocol they've helped popularize, after years of promising interoperability, for reasons that are dubious at best, and in a way that leaves people who don't jump to the new Hangouts app unable to talk to their contacts without any feedback that their IMs aren't getting through... And they've done that with no warning to anyone. I imagine there's a bunch of people out there wondering where some of their buddies have gone, or why their messages aren't getting responses, because this isn't documented anywhere." Google really messed this up. Such a dick move.
Thread beginning with comment 562749
To read all comments associated with this story, please click here.
XMPP is no good for mobile
by soulrebel123 on Sat 25th May 2013 06:43 UTC
soulrebel123
Member since:
2009-05-13

Having worked on XMPP a little, I can tell you that it has two big problems for mobile:

1. it requires a long lived connection
2. it is verbose and wastes a lot of bandwidth.

Anyhow it is an extensible protocol and it could be fixed to a certain point, but most importantly basic functionality could be bridged between the XMPP and the new platform, so that text messages get through.

Reply Score: 7

RE: XMPP is no good for mobile
by terrakotta on Sat 25th May 2013 08:53 in reply to "XMPP is no good for mobile"
terrakotta Member since:
2010-04-21

Any messaging protocol is gonna need a long lived session if you want a push mechanism in place (which for chat you do).

Have you ever used skype, facebook chat, whatsapp, viber.... (ok two of them use (non federated) xmpp) on a mobile? They all drain the battery even when not chatting to anyone.Only text messaging like sms doesn t use much battery when idle, at the cost of draining the battery even more when texting (every text needs a new handshake, which is a lot of data compared to the text sent) and with a high latency as a result.

All these high level protocols are trying to solve a problem that ipv6 does on its own with mobile ip adresses. Solving the problem of dialing someone directly, instead of going through a server (ok, you do need some kind of 'home' router that knows what local ip address you have), but I assume it will be less verbose than having seven tcp sessions open just to be online on all these non compatible networks.

Personally i find myself going back to text messaging more than chatting, just for the sake of compatibility and my smartphones battery life being already too short to begin with. Everyone has a phone nr and it is by far the biggest social network on earth.

Reply Parent Score: 5