Re: [whatwg/fetch] Streaming upload (Issue #1438)

>> Of course, otherwise we wouldn't be here talking about it. Having worked on the Firefox network library in the past (but not currently), I don't see a reason why it can't be done.

> I can not speak to how this would work in Gecko, but from my understanding there is strong pushback from some implementers (specifically Chromium) on anything which doesn't conform to specifically this ordering of events in HTTP: 1. req headers sent, 2. req body sent, 3. resp headers received, 4. resp body received.

That's true for Chromium. I talked about this with other browser vendors at [TPAC 2019](https://docs.google.com/document/d/1q090ovJ4gd8wSfVtvuoZLMZ51YkiFDsEZ0Jiqi41Iys/edit#), their reactions were they would be fine with the half-duplex option, they thought full-duplex would be more difficult.

@benbucksch, what you want is what we call full-duplex in this issue. You could say calling it full-duplex is wrong, but that wouldn't change the situation.

My opinion stays the same. We should make the MVP open to future extentions, ship the MVP as soon as possible, and continue discussing full-duplex at #1254.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/1438#issuecomment-1161763968
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/issues/1438/1161763968@github.com>