- From: Anne van Kesteren <notifications@github.com>
- Date: Mon, 13 Jun 2022 09:47:10 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 13 June 2022 16:47:21 UTC
I'm supportive of exploring a full-duplex solution in #1254. We can still make some tweaks, though I worry that due to blobs we might already expose half-duplex behavior in the API so would need some kind of opt-in as @yutakahirano suggests. And to be clear, I don't think we currently have a concrete proposal for making full-duplex work that is complete/good. As for HTTP/1.1, I'm not sure we ever had multi-implementer support for doing that and we certainly have implementer support for not doing that. The current specification also doesn't really describe how it ought to work. Setting a chunked header doesn't magically chunk the contents. So removing that until we have a concrete proposal for how it ought to work and doesn't run into middleware issues seems good. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/issues/1438#issuecomment-1154151743 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fetch/issues/1438/1154151743@github.com>
Received on Monday, 13 June 2022 16:47:21 UTC