mirror of
https://github.com/tahoe-lafs/tahoe-lafs.git
synced 2024-12-23 14:52:26 +00:00
reveal to clients what data is still required
This lets a client recover from an upload that completes but for which the response is lost (eg because network error or client restart)
This commit is contained in:
parent
16af282c19
commit
61b5c88738
@ -469,10 +469,21 @@ The server must recognize when all of the data has been received and mark the sh
|
|||||||
(which it can do because it was informed of the size when the storage index was initialized).
|
(which it can do because it was informed of the size when the storage index was initialized).
|
||||||
Clients should upload chunks in re-assembly order.
|
Clients should upload chunks in re-assembly order.
|
||||||
|
|
||||||
|
* When a chunk that does not complete the share is successfully uploaded the response is ``OK``.
|
||||||
|
* When the chunk that completes the share is successfully uploaded the response is ``CREATED``.
|
||||||
|
* If the *Content-Range* for a request covers part of the share that has already been uploaded the response is ``CONFLICT``.
|
||||||
|
The response body indicates the range of share data that has yet to be uploaded.
|
||||||
|
That is::
|
||||||
|
|
||||||
|
{ "required":
|
||||||
|
[ { "begin": <byte position, inclusive>
|
||||||
|
, "end": <byte position, exclusive>
|
||||||
|
}
|
||||||
|
,
|
||||||
|
...
|
||||||
|
]
|
||||||
|
}
|
||||||
|
|
||||||
When a chunk that does not complete the share is successfully uploaded the response is ``OK``.
|
|
||||||
When the chunk that completes the share is successfully uploaded the response is ``CREATED``.
|
|
||||||
If the *Content-Range* for a request covers part of the share that has already been uploaded the response is ``CONFLICT``.
|
|
||||||
|
|
||||||
``POST /v1/immutable/:storage_index/:share_number/corrupt``
|
``POST /v1/immutable/:storage_index/:share_number/corrupt``
|
||||||
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
|
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
|
||||||
|
Loading…
Reference in New Issue
Block a user