tus-resumable-upload-protocol
tus-resumable-upload-protocol copied to clipboard
Developer Guide
For some time, we have had the idea of a separate document containing further explanation about the protocol and best practices for implementations which don't fit into the specification. Here are some points which may be contained in this guide:
- Retries (exponential backoff, automated reconnecting etc)
- Single vs multiple requests
- Method overriding
- 100-continue
- Custom extensions
- Checksums
- Header naming scheme (prefix and singular)
- Empty files (length = 0)
- Obtaining upload URL without Creation extension
- Handling 200, 204 and 2xx the same
- Explain tus vocabulary (upload, upload URL, resuming an upload)
- HTTP2 support
If you have further ideas, feel free to comment!
For those stumbling upon this - work on this is being done in #68