BTW, you'll notice that the text has been updated here... http://code.google.com/android/migrating/m3-to-m5/m5-api-changes.html#gtalk
Peter Saint-Andre wrote: > biojab biojab wrote: >> http://code.google.com/android/migrating/m3-to-m5/m5-api-changes.html#gtalk > > First of all, don't panic. > > As I understand it from one of the Android team members, they have been > using XMPP communications (sent only via the Google Talk service) as a > way for developers to debug their code by sending handset-to-handset > messages. This usage was quite limited and the server was hardcoded to > talk.google.com for that reason. This package was never intended for > broader use, e.g. as a general messaging service that could be used for > all the things we're familiar with from the XMPP universe (presence, IM, > RPC, Jingle, etc.). Naturally if developers want a more robust messaging > service that they could hook up to their own XMPP servers, they could > simply use a full XMPP library (a likely candidate is Smack, since > Android is all Java all the time). > > Since Android was never doing anything very extensive with XMPP, it's > not exactly the end of the world that they are more clearly labelling > this package as a GTalk-only debug channel. > > Now, whether it would be better for Android in the long run if they were > doing something more extensive with XMPP is another question... :) > > Peter >
smime.p7s
Description: S/MIME Cryptographic Signature
