Feature/tus

[choonkeat]

Implements http://tus.io/ open protocol for resumable uploads support

cc @khangtoh

[choonkeat]

FYI @winston TUS upload protocol is more suitable for API integration, e.g. mobile app upload big file over flaky network

The only difference with TUS here is that the PATCH response comes with a JSON that the client app should read and store.

[choonkeat]

FYI @zamakkat @shinnyx for clients uploading over unreliable networks, can use the tus.io protocol (which will be 1.0 soonish) on /tus/files endpoint for resumable upload

[winston]

Just to clarify, basically we are implementing the TUS standard/protocol here (headers) right?

[choonkeat]

Yes, but

• TUS protocol is only available at /tus/files end point; does not affect the regular /upload endpoint
• according to protocol, the PATCH response is just HTTP 200 and Offset header (both of which we are doing). But on top of it, we're also returning the json body like what we do for regular attache file upload. This should be a compatible extension to the existing protocol, and I suspect/hope is something not difficult for a client to implement

[winston]

This should be a compatible extension to the existing protocol, and I suspect/hope is something not difficult for a client to implement

Ah yes. There's always the client side story to this too.. Keep forgetting that.