It just depends on what semantics you want. Generally I would recommend using create/destroy or start/stop instead of pause/resume.
If you fail at binding to the service, the service does not exist at all, and you should assume you will never get it. If you fail while calling on to the service (getting a RemoteException back), then for some reason the service's hosting process has disappeared, but the system should restart it a little bit in the future. (Unless it has crashed repeatedly, in which case we stop trying to restart.) On Mon, Aug 31, 2009 at 10:01 PM, droidin.net <bost...@gmail.com> wrote: > > When using AIDL-based async services I've seen various examples when > the service is bound/unbound on Activity's oncreate/ondestroy, onstart/ > onstop and even on onpause/onresume. Which one is "right"? And what is > acceptable recovery strategy when attempt using the service fails? > > Thanks you for your suggestions > > > -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
