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

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

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
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
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
Projects
None yet
Development

No branches or pull requests

1 participant