On 2018-06-27 01:50, Matt Ryan wrote:
Hi,
I have submitted a pull request for a new API feature in jackrabbit-api
at [0]. This addition is intended for use by a new proposed feature for
Oak that allows a client to directly upload or download binaries to/from
a supporting configured blob storage, as described at [1]. A correlated
Oak pull request using this new capability of Jackrabbit is at [2]. (Of
course the PR at [2] won’t build without the change; the original PR
prior to making the change to jackrabbit-api is at [3] if you want to
pull it and try to run it to see how it works.)
Please take a look and let me know what I need to do for this change to
be accepted.
...
Here's a question about *naming*.
Is the feature really tied to HTTP(s)? I don't think so. And if a future
platform used a different protocol, the API wouldn't really need to change.
So maybe all of these interfaces should be named something like
"BinaryAccess*"?
Best regards, Julian
