jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Ryan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-7589) [DirectBinaryAccess][DISCUSS] Client facing API
Date Tue, 24 Jul 2018 19:23:00 GMT

    [ https://issues.apache.org/jira/browse/OAK-7589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16554697#comment-16554697
] 

Matt Ryan commented on OAK-7589:
--------------------------------

[~mreutegg] your suggested changes have been applied.  Much of the client facing API is in
JCR-4335 which is now resolved.  Is there more needed for this issue?

> [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)

Mime
View raw message