I understand that XMPP is used in chat services, but it seems to be more generally useful than that. Can someone list some scenarios and examples where you would consider using XMPP, and the pros and cons of it versus other approaches?
A:
We had a project on collecting information eg. wind direction, temperature, stock and forex, etc. Every sensor is a Jabber 'user'.
- This allows us to detect if a sensor is online, offline or problematic.
- Sensors also publish information to a pubsub node to be distributed to collectors.
- Human users can also interact with a particular sensor by querying with the sensor. The sensor returns human friendly formatted data.
Chuk Lee
2010-10-09 04:20:45
Thanks for your response, Chuk. I guess I was wondering in general what are the use-cases.
Jade
2010-10-15 18:26:08
A:
I know that Dropbox uses it for its filesharing system in Android (possibly it does in other platforms too).
Cons: much more verbose than binary (more bandwidth).
Pros: a wide variety of already implemented client and servers. A wide range of already implemented reliability, scalability, security, presence, rpc, federation, custom components, mail, VoIP mechanisms... the list is very very long. Even if you need something different, and you know where to touch, you could extend it to your needs, inheriting all the already implemented features.
mrrtnn
2010-10-09 06:31:35
Interesting about Dropbox. Thanks for your response, Mrrtnn. I guess I was wondering in general about the use-cases for XMPP. I saw a lot of custom extensions, but when would you choose to use it and when not? The verbosity is a good point.
Jade
2010-10-15 18:27:18
Do you have an example of a use case of the kind you mention? I don't understand your point. Thanks.
mrrtnn
2010-10-17 04:06:31
A:
We use it for chatrooms, and for distributing sports results to users watching live events.
Google Buzz and Facebook talk is built on it.
jrewing
2010-10-21 12:36:28