4 ms·

What makes you say it's not a good mobile protocol? It had some problems in the early 2000s on mobile, but these days it has stream management similar to TCPs a

What makes you say it's not a good mobile protocol? It had some problems in the early 2000s on mobile, but these days it has stream management similar to TCPs and XML compresses very well. As I mentioned in another comment, there are people running it over very low bandwidth HF radio, if it works well there it works well over phones, but I'd be curious to see why people still think otherwise. (Google Talk, naturally, never did implement any of the parts that make it good on mobile, just lilke they refused to do TLS on server to server connections, so note that I'm not arguing that Google Talk was good on mobile, just that if they'd worked on it a bit it could have been)

jayd16 9y ago
What service is using it at scale these days? I can't really think of a popular user. After a certain point it just becomes a headache. When I was working with ejabberd clusters servicing mobile clients it worked but I've had a lot less pain just using a custom protocol over websockets. My personal experience also seems to be mirrored throughout the industry as all the big players eventually move away from xmpp.
- wink 9y ago
  All big players who have an interest in building a walled garden - yes, that sums up "all big players". GTalk was awesome while it was federated.
- rakoo 9y ago
  Most ironically, Google is using it for their Cloud Messaging solution (https://developers.google.com/cloud-messaging/ccs https://developers.google.com/cloud-messaging/ccs and https://firebase.google.com/docs/cloud-messaging/server#choose https://firebase.google.com/docs/cloud-messaging/server#choo... for the replacement) to allow applications to talk with a backend.. The advantages over HTTP are multiple: better battery life, bidirectional communication, asynchronicity. Riot Games is also using it for the messaging part of League of Legends (https://engineering.riotgames.com/news/chat-service-architecture-protocol https://engineering.riotgames.com/news/chat-service-architec...) XMPP is also used by military organisations such as NATO (https://www.isode.com/solutions/military-xmpp.html https://www.isode.com/solutions/military-xmpp.html) The sad truth about XMPP is that it just works, but it has a very bad publicity because there's just no marketing around it, and it's never used directly by users. So it suffers from that wrong image that is just completely outdated.
  - jayd16 9y ago
    You'll notice that the google links mention that the xmpp api is deprecated. I'm not sure what Riot uses these days but the xmpp connection is no longer available to third parties. That sad truth is that people who actually use it end up dropping it. Its not some conspiracy. It just wasn't cutting it.
    - rakoo 9y ago
      It's not XMPP that's deprecated, it's the whole CCS (first link) that's being replaced with Firebase (second link). The XMPP api is still present in the replacement.
      - jayd16 9y ago
        While not fully consistent the XMPP api is referred to as legacy on much of FCM documentation. https://firebase.google.com/docs/cloud-messaging/server https://firebase.google.com/docs/cloud-messaging/server You also misunderstand what this api is referring to. These are APIs for your server to connect to Google's. This is not a direct http and xmpp connection to mobile devices. That's all abstracted away from this.

jayd16 9y ago

What service is using it at scale these days? I can't really think of a popular user. After a certain point it just becomes a headache. When I was working with ejabberd clusters servicing mobile clients it worked but I've had a lot less pain just using a custom protocol over websockets. My personal experience also seems to be mirrored throughout the industry as all the big players eventually move away from xmpp.

wink 9y ago
All big players who have an interest in building a walled garden - yes, that sums up "all big players". GTalk was awesome while it was federated.
rakoo 9y ago
Most ironically, Google is using it for their Cloud Messaging solution (https://developers.google.com/cloud-messaging/ccs https://developers.google.com/cloud-messaging/ccs and https://firebase.google.com/docs/cloud-messaging/server#choose https://firebase.google.com/docs/cloud-messaging/server#choo... for the replacement) to allow applications to talk with a backend.. The advantages over HTTP are multiple: better battery life, bidirectional communication, asynchronicity. Riot Games is also using it for the messaging part of League of Legends (https://engineering.riotgames.com/news/chat-service-architecture-protocol https://engineering.riotgames.com/news/chat-service-architec...) XMPP is also used by military organisations such as NATO (https://www.isode.com/solutions/military-xmpp.html https://www.isode.com/solutions/military-xmpp.html) The sad truth about XMPP is that it just works, but it has a very bad publicity because there's just no marketing around it, and it's never used directly by users. So it suffers from that wrong image that is just completely outdated.
- jayd16 9y ago
  You'll notice that the google links mention that the xmpp api is deprecated. I'm not sure what Riot uses these days but the xmpp connection is no longer available to third parties. That sad truth is that people who actually use it end up dropping it. Its not some conspiracy. It just wasn't cutting it.
  - rakoo 9y ago
    It's not XMPP that's deprecated, it's the whole CCS (first link) that's being replaced with Firebase (second link). The XMPP api is still present in the replacement.
    - jayd16 9y ago
      While not fully consistent the XMPP api is referred to as legacy on much of FCM documentation. https://firebase.google.com/docs/cloud-messaging/server https://firebase.google.com/docs/cloud-messaging/server You also misunderstand what this api is referring to. These are APIs for your server to connect to Google's. This is not a direct http and xmpp connection to mobile devices. That's all abstracted away from this.