LumeWeb
/
tusd
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

read me updates

This commit is contained in:
tim-kos 2013-03-18 17:05:44 +01:00
parent 7ed4ad326b
commit 9e5237683d
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
README.md
View File

@ -37,7 +37,7 @@ feedback](https://github.com/tus/tusd/issues/new). A few potential ideas:
(reverse CDN) (reverse CDN)
* Alternative storage backends: Cloud Files, Dropbox, etc. * Alternative storage backends: Cloud Files, Dropbox, etc.
* More clients: Android, PhoneGap, etc. * More clients: Android, PhoneGap, etc.
* Service integrations: Zencoder, Encoding.com, Youtube, Vimeo, Facebook, AWS * Service integrations: Transloadit, Zencoder, Encoding.com, Youtube, Vimeo, Facebook, AWS
Transcoder, etc. Transcoder, etc.
* File meta data analysis * File meta data analysis
* Thumbnail generation * Thumbnail generation
@ -134,8 +134,13 @@ Range: bytes=0-20,40-99
The `Range` header holds a [byte The `Range` header holds a [byte
range](http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.35.1) that range](http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.35.1) that
<<<<<<< HEAD
informs the client which parts of the file have been received so far. It is informs the client which parts of the file have been received so far. It is
up to the client to choose appropiate `PUT` requests to complete the upload. up to the client to choose appropiate `PUT` requests to complete the upload.
=======
informs the client which parts of the file have #not# been received yet. It is
up to the client to choose appropriate `PUT` requests to complete the upload.
>>>>>>> read me updates
A completed upload will be indicated by a single range covering the entire file A completed upload will be indicated by a single range covering the entire file
size (e.g. `Range: bytes=0-99` for a 100 byte file). size (e.g. `Range: bytes=0-99` for a 100 byte file).