Guoye Zhang
Guoye Zhang
My understanding is `Idempotency-Key` wouldn't be used for resumption. It will only be used for repeating an upload creation procedure as is if the first one failed without any response....
Do we want Upload-Limit to be a dictionary structured field so it can support additional information in the future? E.g. `Upload-Limit: bytes=100000000, concurrency=4`
Would be hesitant defining a min append size. What if the last remaining part is smaller than the min append size? The min size might also interact badly if we...
This is a really good point. Currently, responses to Upload Appending Procedure include the upload offset. We could say something like "if the offset is equal to the size of...
If they don't receive the response, performing an offset retrieving and attempting a resumption (even if it's a 0-length resumption at the end) should be sufficient I think.
It is not currently supported. We need to find good mechanisms for sending data, stream, file, and potentially multipart body, and it will likely be a part of the future...
We currently have these 2: ``` public func upload(for request: HTTPRequest, fromFile fileURL: URL, delegate: URLSessionTaskDelegate? = nil) async throws -> (Data, HTTPResponse) public func upload(for request: HTTPRequest, from bodyData:...
Upload task is a subclass of data task, so there is little difference between the 2 of them. It's recommended to use upload task instead of `httpBody`/`httpBodyStream` properties on the...
We'd also like to integrate with structured fields and provide common structured field accessors. Thought media type constants might better as its own library since it's not HTTP specific. On...