On 26 nov, 21:10, "Tom Gibara" <[EMAIL PROTECTED]> wrote:
> ...
> My preference would be for an web service that allowed 3rd party apps to
> 'share' the update mechanism already used in Google's applications. There
> are lots of difficulties in terms of the scale of that service (something
> that Google can obviously accommodate already) but also issues like
> protecting against abuse of the service by buggy or malicious apps.
>
> It does however present an extremely phone-power efficient solution since
> 'push' system is already running on almost all phones (if not all).
I was thinking about such a standardized system too: it requires the
phone to only have 1 service running for possible dozens of tasks.
Actually I was hoping (since this first SDK) we could use the xmpp
(GoogleChat, or what was it called) for this purpose.
>
> Tom.
>
> 2008/11/26 Mark Murphy <[EMAIL PROTECTED]>
>
>
>
> > MrSnowflake wrote:
> > > What about a IMAP IDLE style of pushing. It too is real pushing,
> > > except your phone needs to keep the tcp connection alive, sending a
> > > NOOP every minutes or so.
>
> > This requires a constant Internet connection, which keeps the GSM radio
> > alive all the time, which drains your battery in no time flat.
>
> > > You could also use xmpp.
>
> > This requires a constant Internet connection, which keeps the GSM radio
> > alive all the time, which drains your battery in no time flat.
>
> > --
> > Mark Murphy (a Commons Guy)
> >http://commonsware.com
> > _The Busy Coder's Guide to Android Development_ Version 1.4 Published!
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
