What problem are you trying to solve?
HTTP offers 1xx status codes, but the Fetch API has no means of exposing them. It only allows one response per request, rather than a stream of any number of responses.
This has a few use cases. For example, it would let web developers implement solutions to #41 and #1626 (the latter of which I am personally interested in) using the Fetch API. Generally, anything using 1xx status codes can be done without them, but the ability to read interim responses allows for performance/network optimizations which are not possible in the browser without more round trips and/or wasted bandwidth.
What solutions exist today?
None. XHR doesn't support this either.
How would you solve it?
It has been proposed to use a solution based on #607.
Anything else?
No response
What problem are you trying to solve?
HTTP offers 1xx status codes, but the Fetch API has no means of exposing them. It only allows one response per request, rather than a stream of any number of responses.
This has a few use cases. For example, it would let web developers implement solutions to #41 and #1626 (the latter of which I am personally interested in) using the Fetch API. Generally, anything using 1xx status codes can be done without them, but the ability to read interim responses allows for performance/network optimizations which are not possible in the browser without more round trips and/or wasted bandwidth.
What solutions exist today?
None. XHR doesn't support this either.
How would you solve it?
It has been proposed to use a solution based on #607.
Anything else?
No response