- From: Luca Casonato <notifications@github.com>
- Date: Mon, 20 Jun 2022 09:11:09 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 20 June 2022 16:11:22 UTC
> Full duplex (in my understanding) means that there are streams in both directions. Not per-se streams - any bi-di communication that does not happen in order. The size of the response body is irrelevant to the discussion about this being half of full duplex. What makes it full duplex is that you are receiving _anything_ from the server before being finished with sending request data. The something you are receiving are the response headers. You are racing the receiving of the response body (which comes after headers, and may be fixed size), with the sending of the request body. You are receiving and sending at once: thus this is full duplex. The definition doesn't really matter anyway, because the point is that what you would require is out of order sending and receiving of data, which is something that browsers are not planning to implement at this time (this is the blocker for #1254). -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/issues/1438#issuecomment-1160629011 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fetch/issues/1438/1160629011@github.com>
Received on Monday, 20 June 2022 16:11:22 UTC