On 27 Ago, 23:58, "Maps.Huge.Info (Maps API Guru)" <[email protected]> wrote: > I think the consensus is that AsyncTask is the way to go if what > you're trying to do affects the UI thread eventually. Using a service > to compute location for instance would be over complicated. > > -John Coryat
Maybe I didn't explain correctly: If I need to react to some location change for example, and notify the user, I can't use _just_ an async thread. I need to to all the logic in a service and throw for example a notification plus a broadcast that will update the ui if it is on top. What I was asking is: if I need to perform more than one task in background (I mean when the phone screen is off, or when the user is reading the times website while sitting on the toilet), does it make any sense to create more than one service? Or should I just create one service that performs many task like listening on the network as well as being notified of position changes? Federico -- 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
