Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: update docs for the multiprocess attribute in provider element

Browse Source 
Bug: 7625079
Change-Id: I671c703c91fc5623ebc3d0645cb7017eb285d27b
This commit is contained in:
Mark Lu
2016-08-30 18:22:20 -07:00
parent 689c92db9d
commit 656fde1875
1 changed files with 8 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
docs/html/guide/topics/manifest/provider-element.jd
View File

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