You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2018/07/03 11:31:00 UTC
[jira] [Commented] (OAK-7589) [DirectBinaryAccess][DISCUSS] Client
facing API
[ https://issues.apache.org/jira/browse/OAK-7589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16531226#comment-16531226 ]
Marcel Reutegger commented on OAK-7589:
---------------------------------------
I updated the summary and description of this issue to better describe the scope of this issue. I'd like to use this issue not just to discuss in which bundle the new package / interfaces will be, but also how they are designed.
The discussion started in [OAK-7570|https://issues.apache.org/jira/browse/OAK-7570?focusedCommentId=16524768&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16524768] should be moved here.
> [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)