From 2bbe51a01d239620bb1d4059fbdf22a709c45ad1 Mon Sep 17 00:00:00 2001 From: Jean-Paul Calderone Date: Thu, 17 May 2018 14:11:37 -0400 Subject: [PATCH] Discuss Range requests for uploads --- docs/proposed/http-storage-node-protocol.rst | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/proposed/http-storage-node-protocol.rst b/docs/proposed/http-storage-node-protocol.rst index b06b3c72f..b97b3c35f 100644 --- a/docs/proposed/http-storage-node-protocol.rst +++ b/docs/proposed/http-storage-node-protocol.rst @@ -168,6 +168,13 @@ 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. +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. +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. ``POST /v1/buckets/:bucket_id/:share_number/corrupt`` !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!