From 656fde18754703d74e1a68595d534dd59fb45749 Mon Sep 17 00:00:00 2001 From: Mark Lu Date: Tue, 30 Aug 2016 18:22:20 -0700 Subject: docs: update docs for the multiprocess attribute in provider element Bug: 7625079 Change-Id: I671c703c91fc5623ebc3d0645cb7017eb285d27b --- docs/html/guide/topics/manifest/provider-element.jd | 20 +++++++++----------- 1 file changed, 9 insertions(+), 11 deletions(-) (limited to 'docs/html/guide') diff --git a/docs/html/guide/topics/manifest/provider-element.jd b/docs/html/guide/topics/manifest/provider-element.jd index 1947849e56f8..0e729c36f37e 100644 --- a/docs/html/guide/topics/manifest/provider-element.jd +++ b/docs/html/guide/topics/manifest/provider-element.jd @@ -215,17 +215,15 @@ it can also be set as a raw string.

{@code android:multiprocess}
-
Whether or not an instance of the content provider can be created in -every client process — "{@code true}" if instances can run in multiple -processes, and "{@code false}" if not. The default value is "{@code false}". - -

-Normally, a content provider is instantiated in the process of the -application that defined it. However, if this flag is set to "{@code true}", -the system can create an instance in every process where there's a client -that wants to interact with it, thus avoiding the overhead of interprocess -communication. -

+
If the app runs in multiple processes, this attribute determines whether +multiple instances of the content provder are created. If true, +each of the app's processes has its own content provider object. If +false, the app's processes share only one content provider object. +The default value is false. + +

Setting this flag to true may improve performance by reducing +the overhead of interprocess communication, but it also increases the memory +footprint of each process.

{@code android:name}
The name of the class that implements the content provider, a subclass of -- cgit v1.2.3-59-g8ed1b