3 ms·
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
by devinfoley 16y ago
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.
- imaginator 16y agoTwitter 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 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.
- devinfoley 16y agoWhat this guy said!