support content uri (e.q. content://xxx) #465
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks. We'll push a change shortly that makes this usable via DefaultUriDataSource as well (DefaultUriDataSource will take http/https/asset/content Uris and delegate to the correct more-specific DataSource implementation). |
ojw28
added a commit
that referenced
this pull request
May 18, 2015
support content uri (e.q. content://xxx)
|
It's great !! Can we consider the empty scheme case ?(e.g. like #467)
|
|
Yeah, I think we should probably assume file:// if the scheme is empty. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In android, content-uri is widely used.
For example, "content://download/" , "content://media/external/video" and so on.
We can query the file descriptor from content resolver and create the input stream from it.