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

Consider looking into Fetch Standard #30

Closed
clue opened this issue Mar 16, 2015 · 2 comments
Closed

Consider looking into Fetch Standard #30

clue opened this issue Mar 16, 2015 · 2 comments
Labels
help wanted new feature
Milestone
v0.5.0

Comments

@clue
Copy link
Owner

clue commented Mar 16, 2015

See: https://fetch.spec.whatwg.org

In particular, it uses a Promise that resolves as soon as the response headers have been received, irrespective of the actual message body.

Also refs #16.
@clue clue mentioned this issue Jun 30, 2015
Merged
@clue
Copy link
Owner Author

clue commented Jun 30, 2015

The fetch standard API might also be a good alternative to the dreaded promise progress API (reactphp/promise#32) that has been implemented with #31.

@clue clue added this to the v0.5.0 milestone Jul 29, 2015
@clue clue mentioned this issue Mar 5, 2016
Closed
@clue clue mentioned this issue Mar 15, 2016
Closed
@clue
Copy link
Owner Author

clue commented Apr 1, 2016

it uses a Promise that resolves as soon as the response headers have been received

This is the main takeaway here.

I've played around with several approaches to a sane streaming API while implementing #46 via #56 and decided to ditch the fetch API for now. See #46 for more details.

@clue clue closed this as completed Apr 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted new feature
Projects
None yet
Milestone
v0.5.0
Development

No branches or pull requests
1 participant
@clue