5 ms·

Why would anybody want to use XMPP with mobile anyways? The protocol is very noisy and as a result it will keep turning your radio on/off in the background, eff

Why would anybody want to use XMPP with mobile anyways? The protocol is very noisy and as a result it will keep turning your radio on/off in the background, effectively killing your battery.

jerf 13y ago
The point is precisely to make XMPP work with mobile. There's no fundamental reason why this is impossible, it just doesn't work very well now. Of course if it is tweaked to work on mobile, well, it will work on mobile after that.
josteink 13y ago
Why would anybody want to use XMPP with mobile anyways? Anyone with an Android-device is already using it. Android's push-notification depends on XMPP to work, and Gtalk/Hangouts is already piggybacking on that, making it a free ride. So, unless you are on the patent-troll side of mobile, you have no reason not to use it.
- nutjob123 13y ago
  >Android's push-notification depends on XMPP to work Do you have a source for this info?
  - ge0rg 13y ago
    In the early Android versions (pre 1.0), the Android API actually included XMPP methods. I also remember reading debug messages containing "XMPP" in the function names related to GCM. These are just hints, and the protocol might have been changed since then, but the GCM uplink feature also indicates that it still at least relates to XMPP.
  - josteink 13y ago
    Not any hard reference-data, but whenever I am on a network where Android-push notification doesn't work, it seems to be because the device cannot connect to talk.google.com on the regular XMPP port, or at least so I seem to remember my logcat telling me. Note: I've observed this without being signed into Google Talk or Hangouts.
- eli 13y ago
  Are you sure about that? http://developer.android.com/google/gcm/index.html http://developer.android.com/google/gcm/index.html talks about using XMPP upstream but I thought the protocol to talk to the device was a lightweight proprietary thing.
  - AceJohnny2 13y ago
    It is. I talked to one of the devs a few years back, and he explained how they used [Protocol Buffers][1] internally, because XMPP just didn't work at their scale. XMPP is a protocol that Google uses in some instances to talk to the rest of the world. But inside their ecosystem, they have no reason to stick to it. [1]: https://developers.google.com/protocol-buffers/ https://developers.google.com/protocol-buffers/
VMG 13y ago
WhatsApp is using a customized version of XMPP: http://en.wikipedia.org/wiki/WhatsApp http://en.wikipedia.org/wiki/WhatsApp
hnha 13y ago
a good client is not really noticeable in battery life for me. have you even tried it or are you just spreading FUD?

Why would anybody want to use XMPP with mobile anyways? The protocol is very noisy and as a result it will keep turning your radio on/off in the background, effectively killing your battery.

jerf 13y ago

The point is precisely to make XMPP work with mobile. There's no fundamental reason why this is impossible, it just doesn't work very well now. Of course if it is tweaked to work on mobile, well, it will work on mobile after that.

josteink 13y ago

Why would anybody want to use XMPP with mobile anyways? Anyone with an Android-device is already using it. Android's push-notification depends on XMPP to work, and Gtalk/Hangouts is already piggybacking on that, making it a free ride. So, unless you are on the patent-troll side of mobile, you have no reason not to use it.

nutjob123 13y ago
>Android's push-notification depends on XMPP to work Do you have a source for this info?
- ge0rg 13y ago
  In the early Android versions (pre 1.0), the Android API actually included XMPP methods. I also remember reading debug messages containing "XMPP" in the function names related to GCM. These are just hints, and the protocol might have been changed since then, but the GCM uplink feature also indicates that it still at least relates to XMPP.
- josteink 13y ago
  Not any hard reference-data, but whenever I am on a network where Android-push notification doesn't work, it seems to be because the device cannot connect to talk.google.com on the regular XMPP port, or at least so I seem to remember my logcat telling me. Note: I've observed this without being signed into Google Talk or Hangouts.
eli 13y ago
Are you sure about that? http://developer.android.com/google/gcm/index.html http://developer.android.com/google/gcm/index.html talks about using XMPP upstream but I thought the protocol to talk to the device was a lightweight proprietary thing.
- AceJohnny2 13y ago
  It is. I talked to one of the devs a few years back, and he explained how they used [Protocol Buffers][1] internally, because XMPP just didn't work at their scale. XMPP is a protocol that Google uses in some instances to talk to the rest of the world. But inside their ecosystem, they have no reason to stick to it. [1]: https://developers.google.com/protocol-buffers/ https://developers.google.com/protocol-buffers/

VMG 13y ago

WhatsApp is using a customized version of XMPP: http://en.wikipedia.org/wiki/WhatsApp http://en.wikipedia.org/wiki/WhatsApp

hnha 13y ago

a good client is not really noticeable in battery life for me. have you even tried it or are you just spreading FUD?