Most of the questions are already answered and I believe you can achieve all that you want with XMPP alone.
Coming back to the question "Help choosing the right technology": if machine to machine communication and light weight messaging transport (especially since you are on mobile) are your top priority, consider investing some time in MQTT. Drawback: Compared to XMPP you won't find enough open source implementations for MQTT, (however the specifications are dead-simple and in no time you can pull off your own client/server implementations) Also, if you are looking to take full advantage of roster/presence/messaging that comes with XMPP, MQTT might not be the right choice for you. -- Abhinav Singh http://abhinavsingh.com/ On 13-Nov-2012, at 1:37 PM, Michael Weibel <[email protected]> wrote: > >> Noting that I'm an expert in neither of these things - APNS is largely >> going to be sending notifications to the user, which is unlikely to be >> useful in a machine<>machine client. GCM seems to be duplicating some >> of the functionality you'd get from the XMPP channel. > > True. > >> It's worth noting that using load testing tools on XMPP servers (at >> least the higher performance ones) almost always leads to performance >> testing of the load testing tools, rather than the server itself, as >> the server will typically process the data faster than the tool will >> send it. > > Yes, that's my experience as well ;) What tsung provides is that you can > relatively easily use multiple machines to do the load testing together which > might lead to actually load testing the servers. > >> They're still useful, though. >> >>>>> Message reliability is very important (as said previously). Also you'll >>>>> need an XMPP library which is robust. There's e.g. asmack[3] for Android >>>>> and e.g. XMPPFramework[4] for iOS. >>>> There are more choices than just these (and these may not be the best >>>> choices). >>> Could you please elaborate on this? As I was searching for libraries I >>> couldn't find a lot more than those. >> >> Being entirely partisan, I'd use Swiften on iOS. There's also a >> Swiften branch for Android (for a C++ interface), and I expect Stroke >> (Java) will support Android pretty soon. I'm sure there are other >> possible libraries, too. > > Interesting. Thanks for the hints. > >> I'm encouraging people to do a bit of digging and see what the options >> are, and not pick the first library/server/client/whatever that's >> mentioned. > > That's indeed important. > _______________________________________________ > JDev mailing list > Info: http://mail.jabber.org/mailman/listinfo/jdev > Unsubscribe: [email protected] > _______________________________________________ _______________________________________________ JDev mailing list Info: http://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: [email protected] _______________________________________________
