Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fetch support for explicit resource management #1741

Open
jasnell opened this issue Feb 27, 2024 · 0 comments
Open

Fetch support for explicit resource management #1741

jasnell opened this issue Feb 27, 2024 · 0 comments

Comments

@jasnell
Copy link

jasnell commented Feb 27, 2024

What is the issue with the Fetch Standard?

This goes along with the streams-specific related discussion here: whatwg/streams#1307

What, if any, support should the fetch spec adopt for explicit resource management (https://github.com/tc39/proposal-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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant