We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Almost Everything is in the title ;-)
ReadableStream from the Stream API is already used in the Fetch API
Streams were also considered for the UDP TCP Socket API via readable and writable UDPSocket and TCPSocket properties.
readable
writable
UDPSocket
TCPSocket
Web Sockets is probably one of the APIs for which such stream API would be the most pertinent
The text was updated successfully, but these errors were encountered:
This was previously discussed at https://www.w3.org/Bugs/Public/show_bug.cgi?id=23992; it's fairly complicated, and mostly redundant with fetch(), it turns out.
Sorry, something went wrong.
Yeah, in fact, using fetch() would give you slightly better performance and it's H2-compatible.
fetch()
Once upload streams are a thing anyway, as per yutakahirano/fetch-with-streams#66.
It seems this would be addressed by #48, potentially.
No branches or pull requests
Almost Everything is in the title ;-)
ReadableStream from the Stream API is already used in the Fetch API
Streams were also considered for the UDP TCP Socket API via
readable
andwritable
UDPSocket
andTCPSocket
properties.Web Sockets is probably one of the APIs for which such stream API would be the most pertinent
The text was updated successfully, but these errors were encountered: