Resume upload with chunk size

[cnlangzi]

Please answer these questions before submitting your issue.

• Why do you submit this issue?
• Question or discussion
• Bug
• Requirement
• Feature or performance improvement

---

Question

---

Bug

---

Requirement or improvement

It is frustrating for a user to upload a large file(eg. video) in single request if there is is loss of connectivity or change of connections from WiFi to Cellular or vice versa. The file should be split into smaller pieces(e.g 64KB), and upload them one by one. It can be resumed when any pieces was failure. This if very helpful. And it should be designed as default mode.

[cnlangzi]

tus is a protocol based on HTTP for resumable file uploads. Resumable means that an upload can be interrupted at any moment and can be resumed without re-uploading the previous data again. An interruption may happen willingly, if the user wants to pause, or by accident in case of an network issue or server outage

• https://tus.io/
• https://github.com/tus/tusd

[guruhubb]

We could potentially use it, but is it an overkill and inefficient for what we want to do with sequenced upload stream? We just need to add a sequence number like we do for downloads to the client. On the blobber side we need to acknowledge the sequence.

[cnlangzi]

It is implemented based on customer header Upload-Length and Upload-Offset . it should be same as a sequence https://tus.io/protocols/resumable-upload.html#statusurl . It seems be more flexible.

[guruhubb]

Would this work for live streaming or very large file migration? If so, go ahead

[cnlangzi]

@guruhubb I will double check, and find a workaround that should be backwards compatible for current gosdk/zboxcli

[cnlangzi]

it is fixed on #344