ExternalVendorCode/tahoe-lafs
1
0
Fork 0
mirror of https://github.com/tahoe-lafs/tahoe-lafs.git synced 2025-02-20 09:46:18 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

when you are sending a range, you use Content-Range

Browse Source 
when you are _asking_ for a range, you use Range
This commit is contained in:
Jean-Paul Calderone 2018-05-17 15:08:03 -04:00
parent 2bbe51a01d
commit 113af95984
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/proposed/http-storage-node-protocol.rst
View File

@ -168,10 +168,10 @@ TODO Verify this conclusion.
Write the share data to the indicated bucket.
The request body is the raw share data (i.e., ``application/octet-stream``).
*Range* requests are encouraged for large transfers.
*Content-Range* requests are encouraged for large transfers.
For example,
for a 1MiB share the data can be broken in to 8 128KiB chunks.
Each chunk can be *PUT* separately with the appropriate *Range* headers.
Each chunk can be *PUT* separately with the appropriate *Content-Range* headers.
The server must recognize when all of the data has been received and mark the bucket as filled.
Clients should upload chunks in re-assembly order.
Servers may reject out-of-order chunks for implementation simplicity.