[
https://issues.apache.org/jira/browse/OAK-7589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-7589:
----------------------------------
Description:
>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.
was: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.
Summary: [DirectBinaryAccess][DISCUSS] Client facing API (was:
[DirectBinaryAccess][DISCUSS] Move API change from oak-jcr)
> [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)
