On 28 Ago, 18:32, Frank Weiss <[email protected]> wrote: > I suppose you'd be better off with a service per service instead of > one god service. The reason is that it make the code cleaner - you > don't need to manage multiple alarms and network connections in one > class. An exception would be a service that just does one kind of > thing, but handles a queue of requests. To avoid copy and pasting > common code, use a common abstract base class that extends Service.
Ok, it's what I wanted to do. One thing that I'd like to get better explained is: I am aware that the service(s) run on the same thread of the ui, so if I have more than one thread will they share the same thread?? If they listen to the same broadcast for example, will the intent be queued and served from one service at the time? It's just curiosity, I know that the time consuming operations must be performed in async tasks or threads. Thanks -- 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
