[
https://issues.apache.org/jira/browse/OAK-7589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16531614#comment-16531614
]
Michael Dürig commented on OAK-7589:
------------------------------------
Here is a quick implementation of how I could envision the approach suggested
above:
[https://github.com/mduerig/jackrabbit-oak/commit/837d9b70547dd29e14291913c5482c0902347834].
This is based on [~mreutegg]'s work proposed earlier and excludes the
permission check as per OAK-7602.
Note that some ITs might be failing as I didn't have the chance to set up the
required fixtures yet.
> [DirectBinaryAccess][DISCUSS] Client facing API
> -----------------------------------------------
>
> Key: OAK-7589
> URL: https://issues.apache.org/jira/browse/OAK-7589
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Reporter: Matt Ryan
> Assignee: Matt Ryan
> Priority: Major
>
> From a discussion w/ [~mreutegg]: Suggested that we move the API changes out
> of oak-jcr (i.e. org.apache.jackrabbit.oak.jcr.api.binary.HttpBinaryProvider
> and org.apache.jackrabbit.oak.jcr.api.binary.HttpBinaryDownload to a
> different package to avoid unnecessary API changes to oak-jcr.
> This issue should also be used to discuss how exactly the client facing API
> is designed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
