You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-commits@jackrabbit.apache.org by ma...@apache.org on 2019/12/04 00:13:09 UTC
svn commit: r1870776 -
/jackrabbit/oak/trunk/oak-doc/src/site/markdown/features/direct-binary-access.md
Author: mattryan
Date: Wed Dec 4 00:13:09 2019
New Revision: 1870776
URL: http://svn.apache.org/viewvc?rev=1870776&view=rev
Log:
OAK-8696: Add link to direct upload algorithm in direct binary access doc
Modified:
jackrabbit/oak/trunk/oak-doc/src/site/markdown/features/direct-binary-access.md
Modified: jackrabbit/oak/trunk/oak-doc/src/site/markdown/features/direct-binary-access.md
URL: http://svn.apache.org/viewvc/jackrabbit/oak/trunk/oak-doc/src/site/markdown/features/direct-binary-access.md?rev=1870776&r1=1870775&r2=1870776&view=diff
==============================================================================
--- jackrabbit/oak/trunk/oak-doc/src/site/markdown/features/direct-binary-access.md (original)
+++ jackrabbit/oak/trunk/oak-doc/src/site/markdown/features/direct-binary-access.md Wed Dec 4 00:13:09 2019
@@ -117,7 +117,7 @@ Also note that clients should always che
The direct binary upload process is split into 3 phases:
1. **Initialize:** A remote client makes request to the Jackrabbit-based application to request an upload, which calls `initiateBinaryUpload(long, int)` and returns the resulting information to the remote client.
-2. **Upload:** The remote client performs the actual binary upload directly to the binary storage provider. The `BinaryUpload` returned from the previous call to `initiateBinaryUpload(long, int)` contains a list of URIs that can be used to upload. Clients use these URIs to upload; however, it is not required for clients to use all the URIs in the list. The number of URIs that must be used is subject to the size of the binary being uploaded and the minimum and maximum sizes returned in the `BinaryUpload` object, which constitutes detailed instructions on how to complete the upload successfully. For more information, see the `BinaryUpload` documentation.
+2. **Upload:** The remote client performs the actual binary upload directly to the binary storage provider. The `BinaryUpload` returned from the previous call to `initiateBinaryUpload(long, int)` contains a list of URIs that can be used to upload. Clients use these URIs to upload; however, it is not required for clients to use all the URIs in the list. The number of URIs that must be used is subject to the size of the binary being uploaded and the minimum and maximum sizes returned in the `BinaryUpload` object, which constitutes detailed instructions on how to complete the upload successfully. For more information, including details on the upload algorithm, see the [`BinaryUpload` documentation](https://jackrabbit.apache.org/oak/docs/apidocs/org/apache/jackrabbit/api/binary/BinaryUpload.html).
3. **Complete:** The remote client notifies the Jackrabbit-based application that step 2 is complete. The upload token returned in the first step (obtained by calling `BinaryUpload.getUploadToken()`) is passed by the client to `completeBinaryUpload(String)`. This will provide the application with a regular JCR Binary that can then be used to write JCR content including the binary (such as an `nt:file` structure) and persist it.
