History log of /frameworks/support/v4/java/android/support/v4/content/FileProvider.java
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
6ac481ae682ce6c374ab7ba646f55f679fdf9afc 21-Jun-2014 Nick Kralevich <nnk@google.com> FileProvider: fix doc link

The existing link is 404ing. Provide the proper link.

Change-Id: I571cee980f1753b2873a76064c74fd26f9854ae6
/frameworks/support/v4/java/android/support/v4/content/FileProvider.java
2304a87017eb4cf2cbe6f1f9e656422dff911962 03-Sep-2013 Joe Malin <jmalin@google.com> Edit FileProvider reference doc for clarity

Change-Id: I8069be2704ea0c0ab5c4c2267130d5cd95fcef38
/frameworks/support/v4/java/android/support/v4/content/FileProvider.java
cdafda9f0228e8cb160a7c873d130dea4bbfea7c 08-Mar-2013 Jeff Sharkey <jsharkey@android.com> Provider to share private files between apps.

Apps should generally avoid sending raw filesystem paths across
process boundaries, since the receiving app may not have the same
access as the sender. Instead, apps should send Uris and rely on
platform features like grantUriPermission() to control access.

This provider is a simple implementation that services Uris which
are backed by raw files on disk. It relies on ContentProvider to
enforce the grants, and supports reading, writing, and deleting. It
responds to OpenableColumns and tries answering getType() using
file extensions.

Apps define supported paths in <meta-data> associated with their
<provider> manifest entries.

Bug: 7005318
Change-Id: Iceb4f2ce996221d2d85e009b62c856dcdf5eca14
/frameworks/support/v4/java/android/support/v4/content/FileProvider.java