On Tue, Feb 18, 2014 at 2:36 PM, Ian Boston <[email protected]> wrote: > Upload the binary via some other mechanism then tell give Oak a > pointer to the location, rather than giving Oak the binary.
Yup. As explained in mail before I am looking for "pass by reference" semantics (somewhat related to JCR-3534). Looking at OAK-834 further. I think we can use that. So instead of custom Binary implementations (as suggested before) the required information is "encoded" in the BinaryReference string and underlying BlobStore can interpret such a url For example to create a Binary out of File object and where client code is transferring the ownership of file to Oak client code can create a ReferenceBinary implementation with following string file://host/path?own=true The underlying BlobStore can - Move the file to its working area - OR efficient copy the file content And then return the Blob Similar scheme can be used by S3DataStore http://<domainname>/objectname ?AWSAccessKeyId =<accesskey>&Expires=<expire time>&Signature =<signature string>&S3=true Above approach can be used with current Oak implementations if BlobStores can support such url. Chetan Mehrotra
