tus/tus-node-server

tus-node-server and ietf

Closed this issue · 11 comments

does this supports latest draft of ietf resumable upload or is there a plan to implement.

I think I'd like to add support for it as it hits working group final call. Supporting draft versions is a bit tricky, as you either make breaking changes for each new draft, or add more complexity to handle multiple versions.

From a developer and user perspective it doesn't really add much, it's just internals that change.

will it be possible without the support of 104 status code as an intermediary response in node and then 201 created.

You're still going to need a client-side library I think. fetch in the browser for instance doesn't expose informational responses. Other than that, from my understanding, at least the major proxies support it as it moves through the network.

So unless you were hoping to use it directly in the browser, I think you'll be fine with the 104 status code.

The informational response is not necessary. A client can send an empty upload creation request and then resume the upload using the returned upload URL, just like how tus uploads are done today.

I want to support ios client which will be using NSURLSession with resumable background upload as introduced in ios17.below is the video related to resumable upload implemented in ios which expects 104 response. its discussed from 10th minute onward.
https://developer.apple.com/videos/play/wwdc2023/10006/

yes, i have checked these example in go and swift and since our backend stack is written in js, i wondered if same could be achieved using node.

@mshafqatprofico wondering if you found a solution for this? We also want to integrate the native iOS implementation which currently only supports the 104 status code approach.

unfortunately not with node. this could help but this will require different backend stack to handle resumable background upload. so i put this on hold. https://tus.io/blog/2023/09/20/tusd-200#support-for-the-new-ietf-protocol

As I mentioned before:

I think I'd like to add support for it as it hits working group final call

From the feedback from the latest sessions I think we're close to reaching that, probably this year. But if you need something right now I wouldn't wait for tus Node.js.

@Murderlon yes, it will be a great feature to add.