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.
-- 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 android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
