[Core] There's no way to find out if transfer is completed on server side

[lleoha]

Let's look at this:

"Clients SHOULD send all remaining bytes of a resource in a single PATCH request, but MAY also use multiple small requests for scenarios where this is desirable"

So how the server is going to know if transfer is completed since it doesn't know how many subsequent patch requests are going to be sent?
It looks like the only way to find out if file is completely transferred is to use POST file creation extension and keep expected file size somewhere.

I think file size to be uploaded should be in the core protocol, since file creation is not specified in the core and does't have to be implemented the way of POST extension. Each PATCH request should be "self-supporting" and should include what is the final file size (especially giving the fact that client knows what the file size is).

[Acconut]

It looks like the only way to find out if file is completely transferred is to use POST file creation extension and keep expected file size somewhere

That's how the current tusd implementation works.

Forcing the client to specify a fixed size at the beginning would conflict with streaming uploads of a variable size (see #16).