-
Notifications
You must be signed in to change notification settings - Fork 39
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
Enhance stream to include network streams #10
Labels
Comments
Maybe instead of everything being a file path, everything is a URL.
I don't know how this would work in the browser with an asynchronous API or for HTTP POSTs where you have to write a payload and then read a response. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the standard restricts the meaning of streams to file streams. The underlying idea is a Plan 9-like design aesthetic in which everything is a file. This should be extended to any kind of streaming data, the interpretation of which is at the discretion of the port author.
This requirement by the standard is restrictive when dealing with environments, like JS, that don't have a concept of files.
The text was updated successfully, but these errors were encountered: