[
https://issues.apache.org/jira/browse/OAK-7570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16539664#comment-16539664
]
Marcel Reutegger commented on OAK-7570:
---------------------------------------
bq. Some questions regarding the whiteboard approach: How do you know this is
the one from the BlobStore/DataStore used by the NodeStore?
That's the beauty of it. The oak-jcr layer doesn't need to know where it comes
from. Loose coupling gives you the freedom to combine components in different
ways.
bq. Can this be used to add a HttpBlobProvider in an OSGi context at runtime,
outside Oak? If yes, is this something that should be allowed?
I think this is no different from registering a NodeStore or BlobStore. If this
is a concern, then resolving bundles that want to make use of those interfaces
can be restricted with an OSGi ResolverHook.
> [DirectBinaryAccess][DISCUSS] How to access HttpBlobProvider from oak-jcr
> -------------------------------------------------------------------------
>
> Key: OAK-7570
> URL: https://issues.apache.org/jira/browse/OAK-7570
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: jcr
> Reporter: Matt Ryan
> Assignee: Matt Ryan
> Priority: Major
>
> Open discussion related to OAK-7569:
> The [original pull request|https://github.com/apache/jackrabbit-oak/pull/88]
> proposes changes to oak-api, oak-segment-tar, oak-store-document, oak-core,
> and oak-jcr as well as oak-blob-plugins, oak-blob-cloud, and oak-blob-azure.
> Would it be possible / better to keep the changes local to the oak-blob-*
> bundles and avoid making changes throughout the stack?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
