ansaurus

Question

Answer 1

+1 A:

What use case would using stopSelf(int) fall under?

Step #1: Call startService()

Step #2: Call startService() again

Step #3: Call stopSelf()

At this point, we want the service to not be stopped, since there is still work outstanding, represented by the second startService() call. We want the startService() and stopSelf() calls to match.

CommonsWare 2010-08-30 06:55:09

Oh, I think I get it. I think I'm overthinking this. So we would just store startId to a global variable whenever onStartCommand() gets executed, and then call stopSelf(int) on that global variable. Ok gotcha. I was trying to thinking about putting the IDs into a synchronous queue or something lol

Falmarri 2010-08-30 07:01:18

@Falmarri: "So we would just store startId to a global variable whenever onStartCommand() gets executed" -- no, since there will be several of these. You may wish to examine `IntentService` and consider whether that is a better base class for you to use. It handles the `stopSelf(int)` calls itself, among other features.

CommonsWare 2010-08-30 07:06:24

Hmm, then I guess I'm still confused. How would you go about handling it yourself? Is there an example? I haven't seen any use of the startId in any examples

Falmarri 2010-08-30 07:16:27

@Falmarri: You pass `startId` as a parameter around your code, until you get to the point where you need it for `stopSelf()`.

CommonsWare 2010-08-30 07:35:27

ansaurus

tags:

views:

answers:

Android service startId parameter

related questions