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

Rebuild on top of the WHATWG Streams API #14

Open
jcranmer opened this issue Sep 27, 2015 · 2 comments
Open

Rebuild on top of the WHATWG Streams API #14

jcranmer opened this issue Sep 27, 2015 · 2 comments

Comments

@jcranmer
Copy link
Contributor

https://streams.spec.whatwg.org/

Unfortunately, the API is still not stable, nor is it actually implemented anywhere in the browser. This will constitute a major, breaking API deviation, but until the specification looks stable, I'll continue using the deliverData/deliverEOF combos I've been using.

(For bonus points: work out how to represent the handler of MimeParser with the streams API).

@lygstate
Copy link

What's the advantage of Streams API

@jcranmer
Copy link
Contributor Author

The Streams API is what will (hopefully) come out naturally for things like file or socket I/O, and there are aspirations for being able to pass streams across worker boundaries.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants