Re: [whatwg/fetch] Developer-controlled streams for request/response (#88)

> In other words, it's perfectly fine to send a response before you've received the entire request, but it can only depend on the parts of the request received up until that point. True bi-di would mean that later parts of the response depend on later parts of the request.

I'm not sure how you derive this interpretation from that one paragraph which appears to just talk about sending `connection: close`.

> Anyway, I don't want to get into standards-lawyering. Standards can be changed. Real-world compatibility is far more important.

I don't think anyone here is standards-lawyering, I am genuinely interested in the standard prevents bi-directional communication. I would expect something like "The server must wait until the entire request is received before sending the response" or something to that effect.

I also agree that real-world compatibility is important.

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