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.

Sign up for GitHub

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

Jump to bottom

how to make request / response stream ? #13

Closed
Jxck opened this issue Nov 9, 2014 · 2 comments
Closed

how to make request / response stream ? #13

Jxck opened this issue Nov 9, 2014 · 2 comments

Comments

@Jxck
Copy link

Jxck commented Nov 9, 2014

current fetch api spec says

it is currently lacking when it comes to reporting progression.

I think this solves when response will supports stream api of whatwg.
but there is no spec about that, only returns promise and resolve only once.

do you currently have any idea about this ?
or any point of discussion about this ?
@domenic
Copy link
Member

domenic commented Nov 9, 2014

Current plan is at https://github.com/yutakahirano/fetch-with-streams/ :)

@Jxck
Copy link
Author

Jxck commented Nov 9, 2014

thanks 👍

@Jxck Jxck closed this as completed Nov 9, 2014
yutakahirano added a commit that referenced this issue Jun 23, 2020
@yutakahirano
# This is a combination of 2 commits.
db9fbcd 
# This is the 1st commit message:

# This is a combination of 23 commits.
# This is the 1st commit message:

Integrate CORP and COEP

This is part of the introduction of COEP
(whatwg/html#5454). The CORP check now takes
COEP into account. Also, responses coming from service workers
are checked.

# This is the commit message #2:

Update fetch.bs

Co-authored-by: Domenic Denicola <d@domenic.me>
# This is the commit message #3:

Update fetch.bs

Co-authored-by: Domenic Denicola <d@domenic.me>
# This is the commit message #4:

fix

# This is the commit message #5:

fix

# This is the commit message #6:

fix

# This is the commit message #7:

fix

# This is the commit message #8:

fix

# This is the commit message #9:

fix

# This is the commit message #10:

fix

# This is the commit message #11:

fix

# This is the commit message #12:

fix

# This is the commit message #13:

fix

# This is the commit message #14:

fix

# This is the commit message #15:

fix

# This is the commit message #16:

fix

# This is the commit message #17:

fix

# This is the commit message #18:

Update fetch.bs

Co-authored-by: Anne van Kesteren <annevk@annevk.nl>
# This is the commit message #19:

Update fetch.bs

Co-authored-by: Anne van Kesteren <annevk@annevk.nl>
# This is the commit message #20:

fix

# This is the commit message #21:

fix

# This is the commit message #22:

fix

# This is the commit message #23:

fix

# This is the commit message #2:

fix
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Jxck @domenic