On Feb 19, 4:51 pm, Bobby <bobb...@gmail.com> wrote:

I absolutely agree that the XMPP shouldn't be tied to a specific set of servers...thus all that I've said about walled gardens and how utterly evil they are. But making an XMPP service as part of the core of android (android.net.xmpp since there's already an android.net.http, right?) doesn't mean it has to be tied to google's servers. Maybe default to @gmail.com in the XMPPService config, if they want to try to boost their own service, but if I blank that out and put in my own server, it absolutely should work with it.

No, I think it would be fantastic if the carriers set up their own XMPP servers to use with the core XMPPService. I think that would be a most fantastic result of a core XMPP service in android. If they don't want to do that, then they can default to google's servers, there are all sorts of deployment possibilities. What's important is that the XMPP capabilities be a core part of the system, otherwise you get, "You're having trouble with app xyz? Oh, you must have the XMPPService from foo.org installed, our app is only compatible with the XMPPService from bar.org." Or worse, "Our app uses Ajax."

Shoot...if you do that, you could even make some real progress on dealing SMS the death it so rightly deserves!

Oh, I don't know...I thought it was called the Open Handset Alliance and used the android.* hierarchy. Call me crazy. *shrug*