That's all I need to know - that the stopping of the Content Provider
cannot be controlled by the user.
Thanks Dianne.
On Oct 22, 11:02 am, Dianne Hackborn hack...@android.com wrote:
The content provider needs to be running the entire time its hosting process
is running. There is no way
Doesn't that happen anyway?
If memory is low, Android starts closing all kinds of process down.
But it will do so on its own terms and time :-)
On Oct 21, 8:26 pm, B++ bet...@gmail.com wrote:
The Content Provider starts when the first applicable URI is resolved.
This will make the
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
3 matches
Mail list logo
