Lines Matching full:contentprovider
37 <li> <a href="#ContentProvider_for_download_UI">ContentProvider for download UI</a>
197 <tr><td > <code>com.android.providers.downloads.DownloadProvider</code> </td><td > Extends <code>ContentProvider</code>, can't be eliminated. </td></tr>
264 <h3><a name="ContentProvider_for_download_UI"> </a> ContentProvider for download UI </h3>
274 Getting rid of <code>OTHER_UID</code> would be beneficial for the download manager, but the existing functionality has to be worked around. At this point, the idea that I consider the most likely would be to have checkin and market implement =ContentProvider= wrappers around their downloads, and expose those content providers to whichever app they want, with whichever security mechanism they wish to have.
494 The primary interface that applications use to communicate with the download manager is exposed as a ContentProvider.
729 <tr><td > <code>com.android.providers.downloads.DownloadProvider extends ContentProvider</code> </td></tr>
742 The download manager is built primarily around a ContentProvider and a Service. The ContentProvider part is the front end, i.e. applications communicate with the download manager through the provider. The Service part is the back end, which contains the actual download logic, running as a background process.
