Michael Dale wrote:
I would add systems like Firefogg help a bit with
chunked uploading
letting us accept larger files by breaking it up into 1 MB POST chunks
on the client side.
Also new-upload-api has improved http copy upload support so if the
500MB Tiff or 5GB .ogg was ftp uploaded to a remote server with http
serving, it could then be ingested over http download rather than POST
upload. (which would be more resource friendly / reliable with large files)
--michael
Not really an addition since I already mentioned them ;)
Upload from URL and Firefogg should alleviate the
issue, though.
Are the "1 MB POST chunks" just rfc2616 chunked transfer-coding applied
to a POST body, or is it a custom protocol using several POSTs?
There's a upload.txt file on docs/ but it's not any helpful.