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

An HTTP/1.1 client can presumably terminate a streamed request by producing a last chunk for the purpose of reusing the same connection. I can't see how HTTP/1.1 makes anything harder (in theory) except that many implementations probably don't have much interest to touch their HTTP/1.1 code. 

For browsers, is it common to change the run-time behavior based on the HTTP protocol version? The algorithm would be simpler if early-response data is delivered to the app regardless of the negotiated protocol  ...  or not?

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