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.

I also want to once again clarify that I don't care about upload streaming with the above mentioned ordering of events at all. I don't have any usecases for it. I am only involved here to ensure we don't accidentally close the door to out of order (full duplex) communication in the future.

> If you spec it as https://github.com/whatwg/fetch/issues/1438#issuecomment-1158981343, it would be unusable for exactly that one case which absolutely needs streaming uploads and which cannot be done at all currently.

I disagree you can not do it, but I agree it's not ideal and you probably shouldn't do it. As stated above, I think ordered half duplex communication as I proposed above is not very useful. Chromium however wants to ship something, and can not currently ship full duplex (or anything where HTTP event ordering isn't ordered as described above), so our choices are currently to do either:

1. Do nothing, and wait until Chromium comes around to full duplex support.
2. Ship half duplex as specified above, and leave full duplex to later.

In no scenario are we getting full duplex right now.

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

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