[
https://issues.apache.org/jira/browse/OAK-7589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16524089#comment-16524089
]
Marcel Reutegger commented on OAK-7589:
---------------------------------------
In my view there are two viable options:
- Move the new interfaces to a new module that can be released independently.
This new module can then also be advertised and used as the API for this
feature. Application code would then depend on this new API module in addition
to the JCR API to use the feature. The new module could be released with a
stable version even before an implementation is available. The downside is,
this will spread the API across more modules and requires individual module
releases, which would be something new to Oak. Though, it is where Oak wants to
go in the future anyway.
- Introduce a new package in jackrabbit-api with the new interfaces. Note, this
doesn't mean classic Jackrabbit must implement it. This approach comes with
less overhead because the package is added to an existing module. The downside
is the release dependency this introduces for this feature between Jackrabbit
and Oak. A Jackrabbit release will be required before work in Oak can be
committed. However, this dependency already exists between the two projects.
The issue with this approach may be client code that doesn't want to depend on
unstable releases. They will have to wait until there is a new stable
Jackrabbit release.
My preference is adding the new package to jackrabbit-api. This makes it easy
for clients to adopt (simply update to a new jackrabbit-api version) and gives
clear indication that this is an extension to the JCR API.
> [DirectBinaryAccess][DISCUSS] Move API change from oak-jcr
> ----------------------------------------------------------
>
> 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 message was sent by Atlassian JIRA
(v7.6.3#76005)
