-
Notifications
You must be signed in to change notification settings - Fork 349
Creating new request & response objects could be easier #771
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
Comments
Otherwise, I need to export https://fetch.spec.whatwg.org/#concept-response-trailer-promise. |
I guess you're talking about the platform objects, not the concepts? It's probably good to introduce an abstraction for them, yes. |
Yeah, I mean the platform objects. I'm doing this for background fetch https://wicg.github.io/background-fetch/#create-settled-fetches-algorithm. I'm attempting a more specific description of how requests/responses come out of the cache. |
I guess service workers and the cache API need this too in some way. Should probably take that into account too. |
In specs, if I want to create a new request, I'm creating the request object, then creating the headers object, then hooking the two up.
With responses it's slightly more complicated, as I need to deal with the trailer promise too.
Is this worth simplifying?
The text was updated successfully, but these errors were encountered: