Very interesting. This may also be useful if one writes a general background service that allows different GUI activities to access it, but one does not want to single out a particular GUI.
In this case, it would be really advantageous to publish the intents used, for example in the OpenIntents intents registry http://www.openintents.org/en/intentstable , so that other developers can also use the intents :-) Peli www.openintents.org On Sep 25, 5:52 pm, "Jeff Hamilton" <[EMAIL PROTECTED]> wrote: > There isn't anything preventing you from doing this. You could, for > example, have an application that consisted of just a Service and a > BroadcastReceiver and have the receiver start the service when > something interesting happens. > > -Jeff > > On Thu, Sep 25, 2008 at 6:23 AM, Graeme <[EMAIL PROTECTED]> wrote: > > > Hi > > > Since an Activity does not need to provide a User Interface at all, > > does this mean > > that an Android application can be a background Service ? I 'm not > > sure why one > > would want to do this, but is it possible ? I imagine one Activity > > (which did not create > > a User Interface) would be needed as a point-of-entry, this Activity > > could just essentially > > launch a Service component. > > > Thanks for any insights > > Graeme --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
