Re: [fetch] Support full-duplex HTTP streaming (#229)

Just some background / random thoughts FWIW --

Using "full duplex" here is at best confusing.

It's true that a HTTP/2 stream is fully duplexed, but that's completely separated from how HTTP *uses* the streaming layer.

I think what's being asked for is the ability to consume the response body before the request has been completely sent.

Both HTTP/1 and HTTP/2 allow that, although from what we saw at the time, some implementations -- including browsers -- of HTTP/1 have a harder time doing that in practice. HTTP/2's multiplexing makes it easier to write an implementation that allows this.

So, I think it's completely reasonable to make this explicit in Fetch, but you might want to check and see how well it's supported in browsers first. 

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/229#issuecomment-191463972