- From: James M Snell <notifications@github.com>
- Date: Tue, 27 Feb 2024 09:13:45 -0800
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 27 February 2024 17:13:50 UTC
### What is the issue with the Fetch Standard? This goes along with the streams-specific related discussion here: https://github.com/whatwg/streams/issues/1307 What, if any, support should the fetch spec adopt for explicit resource management. I'm specifically thinking of the `Request` and `Response` objects here. Let's focus tho more generally on anything that includes the `Body` mixin... Should `Body` be disposable and what would that mean? ``` using response = await fetch('http://example.org'); ``` Specifically, if the body payload has not been fully read, would dispose cancel the remaining read and cause outstanding promises to be rejected? Or should `Request`/`Response`/`Body` just not be disposable? -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/issues/1741 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fetch/issues/1741@github.com>
Received on Tuesday, 27 February 2024 17:13:50 UTC