Glenn Strauss

Sample (not too detailed) * Step 1: send request to create temporary resource via well-known URI. * Step 2: send multiple requests to populate temporary resource. Partial-PUT is well-defined for...

I should add that with happy-eye-balls, a request to the target resource with the request body could be made in parallel to a request for a temporary resource. If the...

> How is this proposal better than the current solution? Infinitely. * Much more robust. There is a separation of concerns between temporary resource creation and submission. * Temporary resource...

There's no reason the request could not also include a structured field with parameters to more precisely communicate with the server the intended properties and use of the generic temporary...

I might not have time to submit that until mid-Sept. I hope I have submitted enough actionable feedback that more discussion is warranted with the WG and last call on...

> More detail as to why this is fragile would help. Hyperbolic statements do not. Section 4.6 Concurrency > The RECOMMENDED approach is as follows: If an upload resource receives...

My proposal side-steps all the complexity by suggesting that the client adjust the data chunk size of the representation that it chooses to send. By not requiring serial upload, the...

> So the answer to my question > > > Does your proposal offer any way to avoid such resource spending by allowing a a client to get an accurate...

> What is the client is sending in parallel? Is there a way to query the precise ranges that have been processed and received? > > A server can respond...

> Your design, IIUC, requires a 2xx to confirm the chunks are received in whole. It's all or nothing. One might say very HTTP-like. The difference from all-or-nothing is that...