Support for Content scheme URIs for Android about kamel HOT 3 OPEN

Hey @luca992, I think this one would be doable with mappers too once we address #70 since android.net.Uri could either be a local file or a remote uri too, just as NSURL on #71 .

from kamel.

Sounds like it could be a good feature to add. I don't really have time to look into this atm, but if you want to do a pr, context is now injected into kamel-core here. Or LocalContext.current possibly could be used as well...

I believe it could be implemented as a new type of fetcher: Fetcher<android.net.Uri>. For example this is the HttpFetcher.

Basically Fetcher<android.net.Uri> just specifies a data source type android.net.Uri in this case and fetches bytes bytes from it.

Also, fyi Fetcher is an interface you can implement in your own app and add to your own KamelConfig without having to make a PR here. But if you do implement it and want to share, please do. PR's are always welcome!

In some cases on android your could probably just accomplish this as well with a mapper... if you can actually get a real file path from android.net.Uri ... but I know in many cases android's Storage Access Framework (which is difficult to say the least) prevents you from doing anything but reading the bytes. In which case a Fetcher would be the way to go.

from kamel.

Hey @luca992, I think this one would be doable with mappers too once we address #70 since android.net.Uri could either be a local file or a remote uri too, just as NSURL on #71 .

Yup for sure

from kamel.