Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upAdd some api for web readable streams #907
Comments
This comment has been minimized.
This comment has been minimized.
|
It sounds like a great idea to figure out how to turn node.js streams into W3C streams. I'm surprised there isn't a module for this already. Want to go write it? I don't think this belongs in the library itself, though. Node.js streams work well and they're by far the most widely used stream implementation. I'm happy to reconsider this if W3C streams get a ton of adoption. |
This comment has been minimized.
This comment has been minimized.
|
It looks like |
This comment has been minimized.
This comment has been minimized.
|
hmm, interesting. Maybe wish he rather built a conversion api instead of depending on web-stream-polyfill |
This comment has been minimized.
This comment has been minimized.
|
This thread has been automatically locked because it has not had recent activity. To discuss futher, please open a new issue. |
Given that it's all about using torrent in the web i think it would make since to support the standard web stream also.
Not saying we should go and replace the hole node stream and go with web streams instead.
But for a way to get it as a instance of ReadableStream from the api so that it can be consumed by the new FileSystem api, fetch upcoming streaming upload, to streamsaver and all new stuff that i don't know about yet