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

Supporting for HTTP/1.1 might be an overreach though its worth discussing. For HTTP2 though we should be fine as it's already in spec.

For HTTP/1.1:
No pipelining is not what is meant here. Its literally a server that responds with payload before the client has sent the last bytes of the request. Servers (potentially out of spec ones) can do this today anyway and I'd be curious to know how much of the web that actually breaks . HTTP clients & proxies already have to tolerate full-duplex IO for Expect/Continue handling so it might not actually break all that much.

All that said I would be totally fine with HTTP2 only given that the web is rapidly moving in that direction anyway.

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