Marcel Reutegger commented on OAK-7570:

bq. It really is an extension of _the_ Blob/DataStore. It is not supposed to be 
some separate component that someone else could provide...

If you tie it to the BlobStore directly, then you are right. But it doesn't 
have to be that way. With a HttpBlobProvider independent of the BlobStore, the 
HTTP access can be decoupled from the BlobStore. Not all of them have 'native' 
HTTP support. What if I want to implement direct binary access for the 
filesystem datastore? I would rather not want to implement this aspect in the 
current filesystem datastore, but instead have a separate component that issues 
a secure URI for a HTTP endpoint that has access to the filesystem of the 

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

Reply via email to