Also, unlike a regular service, an IntentService does in fact run the task in the background. (one task at a time)
On Thursday, August 8, 2013 4:05:07 PM UTC+3, Streets Of Boston wrote: > > For option 2, use an IntentSerrvice. Then you don't have to worry about > calling 'stopService'. It does it for you when necessary. > > > On Thursday, August 8, 2013 7:40:02 AM UTC-4, ashish wrote: >> >> I read about services in Android very carefully, but I didn't find any >> valid reasons to use it. E.g. >> >> 1. >> >> By default services run in the main thread, which most of the >> applications don't want. >> 2. >> >> A service can run on a seperate thread if it spawns it own thread. >> But if a service runs on a seprate thread, then the method >> stopService(new >> Intent(getApplicationContext(), MyService.class)); does not stop the >> running service. Again this is a problem. >> >> If we want to do some background operations, then I think threads are >> better than services. Am I right? >> > -- 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 --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
