docs: update docs for the multiprocess attribute in provider element am: 656fde1875 am: 9bcd53d099 am: a2a3d9e4ea

am: 7cb1d7bc99

Change-Id: Ic9e5b6a06881b920234577e5be380b2a8919b25d
This commit is contained in:
Mark Lu
2016-09-29 03:24:39 +00:00
committed by android-build-merger

View File

@@ -215,17 +215,15 @@ it can also be set as a raw string.
</p></dd> </p></dd>
<dt><a name="multi"></a>{@code android:multiprocess}</dt> <dt><a name="multi"></a>{@code android:multiprocess}</dt>
<dd>Whether or not an instance of the content provider can be created in <dd>If the app runs in multiple processes, this attribute determines whether
every client process &mdash; "{@code true}" if instances can run in multiple multiple instances of the content provder are created. If <code>true</code>,
processes, and "{@code false}" if not. The default value is "{@code false}". each of the app's processes has its own content provider object. If
<code>false</code>, the app's processes share only one content provider object.
The default value is <code>false</code>.
<p> <p>Setting this flag to <code>true</code> may improve performance by reducing
Normally, a content provider is instantiated in the process of the the overhead of interprocess communication, but it also increases the memory
application that defined it. However, if this flag is set to "{@code true}", footprint of each process.</p></dd>
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.
</p></dd>
<dt><a name="nm"></a>{@code android:name}</dt> <dt><a name="nm"></a>{@code android:name}</dt>
<dd>The name of the class that implements the content provider, a subclass of <dd>The name of the class that implements the content provider, a subclass of