alexvanin/distribution
1
0
Fork 0
forked from TrueCloudLab/distribution
Code Pull requests Activity

patch #222 to api.md.tmpl

Browse source
This commit is contained in:
xiekeyang 2015-03-05 13:12:27 +08:00
parent 91403c1b52
commit 4f9a6782bb
1 changed files with 4 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
doc/spec/api.md.tmpl
View file

@ -19,9 +19,9 @@ reduce bandwidth usage and decrease the likelihood of backend corruption.
For relevant details and history leading up to this specification, please see
the following issues:
- docker/docker#8093
- docker/docker#9015
- docker/docker-registry#612
- [docker/docker#8093](https://github.com/docker/docker/issues/8903)
- [docker/docker#9015](https://github.com/docker/docker/issues/9015)
- [docker/docker-registry#612](https://github.com/docker/docker-registry/issues/612)
### Scope
@ -367,8 +367,7 @@ used to key the last used location header when implementing resumable uploads.
The progress and chunk coordination of the upload process will be coordinated
through the `Range` header. While this is a non-standard use of the `Range`
header, there are examples of [similar approaches](https://developers.google.c
om/youtube/v3/guides/using_resumable_upload_protocol) in APIs with heavy use.
header, there are examples of [similar approaches](https://developers.google.com/youtube/v3/guides/using_resumable_upload_protocol) in APIs with heavy use.
For an upload that just started, for an example with a 1000 byte layer file,
the `Range` header would be as follows: