-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sorry folks, this thread is just getting sillier by the minute. *IF* google does not want to do this, why can't you all
get together and implement *exactly* the same API that was there in the previous rev with exact same semantics.

After all (1), we know exactly what was used to implement this API [1] and we have prototype code that worked in the
previous SDK [2].

After all (2), this is supposed to be an "open source" platform

Is there really an itch here or just a wish that someone else (google) should shoulder the burden...

[1] http://www.igniterealtime.org/projects/smack/index.jsp
[2] http://davanum.wordpress.com/2007/12/31/android-just-use-smack-api-fo...

| More discussion on the subject, and I have to say I agree with the
| comments there as well. XMPP inclusion was what excited me most about
| Android and this is a major let down...
|
| http://code.google.com/p/android/issues/detail?id=201
|
| Mike
|
|
|
|
| On Feb 15, 12:00 pm, hackbod <hack...@gmail.com> wrote:
|> On Feb 15, 10:19 am, fry <bender...@gmail.com> wrote:
|>
|>> If I would like to create my own Jabber IM client, it would be weird
|>> if I have to build it over API of another IM client (gtalk) - even if
|>> "com.google.android.gtalkservice" would contain same classes as
|>> "com.google.android.xmppService" did, it would still look weird.
|> We are actually fairly careful about what is part of the generic
|> platform, and what is not.  Specifically, things in the com.google.*
|> namespaces are Google-specific APIs that are not part of the core
|> platform: that is, you can create a device without any of the Google
|> services in those namespaces and still have a working system.  This is
|> why they are listed in the separate "Google APIs" part of the
|> documentation.  Correspondingly, given a device that doesn't include
|> the APIs, a third party can install on that device a separate .apk
|> that provides the same features and works just like the one we are
|> shipping with our platform.
|>
|> I can't address the specific situation of XMPP or GTalk, but I wanted
|> to give an overview of where these fit in to the larger platform
|> picture.  In general, I don't think these are APIs that we can provide
|> as a standard part of the platform, since they rely on an external
|> service that may not be available.  In this sense they are very
|> different than SMS, which is a standard feature available to every
|> phone.
| |
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)

iD8DBQFHti5ygNg6eWEDv1kRAt61AKCoIww0pFkoq0O3EmwzIACUwoD7YwCgt8Q0
ijwgR+oVf2pbBYfcONxSJn8=
=vSSJ
-----END PGP SIGNATURE-----