Yes, whatever process you are in, the main thread needs to be kept responsive.
Also, for what it's worth, I would recommend against running things in separate processes unless there is a really strong direct reason to do so. Our current baseline overhead for a process is unfortunately about 2mb, so a process is an extremely heavy-weight entity. On Fri, Nov 21, 2008 at 1:33 PM, sandy8531 <[EMAIL PROTECTED]> wrote: > > I have a service which I start off in a separate process from the > application using "process:myname" tag. > > Do I need to be careful to take longish running method calls out of > the main thread, even when the service is in its own process ? I do > some initialization during onCreate/onStart that could take a few > seconds. I would like to understand what is the implication of > leaving these calls here, or should I take these calls off on to a > separate thread. > > > > > > -- Dianne Hackborn Android framework engineer [EMAIL PROTECTED] Note: please don't send private questions to me, as I don't have time to provide private support. 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 [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 -~----------~----~----~----~------~----~------~--~---
