The content provider needs to be running the entire time its hosting process is running. There is no way around this. Otherwise, there are all kinds of deadlocks that can happen due to the fact that interaction with a content provider is synchronous. I don't really understand the second part of your question. Processes are killed when they are not needed and their memory is needed elsewhere. If process has a content provider running in it, but no other processes are using that provider, then the process is not needed and will not be kept around.
On Wed, Oct 21, 2009 at 5:26 PM, B++ <[email protected]> wrote: > > The Content Provider starts when the first applicable URI is resolved. > This will make the ContentProvider run forever and there doesn't seem > to be a way to stop it (such as due to inactivity etc). It would be > nice if Content Provider would stop after some time so that the > memory usage is reduced (An enclosing process, doesn't need to be > alive if the Content Provider is not needed anymore). > > Any idea? > > > > > -- 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, 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 [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 -~----------~----~----~----~------~----~------~--~---
