On Sun, Sep 12, 2010 at 5:23 AM, Federico Paolinelli <[email protected]> wrote: > I think a classic service would be more suitable than an IntentService > for this purpouse.
Correct. > The intent service, and therefore your wakeful one, does its job and > then dies after the onHandleIntent is called. > If you implement a locationlistener, you'll never know (or, you can't > predict) when you will get the first location update (which is also > the one you need, at least until the next alarm triggering), so you > need something that stays alive until it gets the first fix. Also correct. > However, also in this situation, I can start the service and make it > kill himself where the location is found (or after a reasonable amount > of time). Still correct. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android Training...At Your Office: http://commonsware.com/training -- 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
