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

Add readable and writable stream properties to Web Socket API #49

Open
AMorgaut opened this issue Sep 27, 2016 · 4 comments
Open

Add readable and writable stream properties to Web Socket API #49

AMorgaut opened this issue Sep 27, 2016 · 4 comments
Labels
addition/proposal New features or enhancements

Comments

@AMorgaut
Copy link

AMorgaut commented Sep 27, 2016

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.

Web Sockets is probably one of the APIs for which such stream API would be the most pertinent

@domenic
Copy link
Member

domenic commented Sep 27, 2016

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.

@annevk
Copy link
Member

annevk commented Sep 28, 2016

Yeah, in fact, using fetch() would give you slightly better performance and it's H2-compatible.

@annevk
Copy link
Member

annevk commented Sep 28, 2016

Once upload streams are a thing anyway, as per yutakahirano/fetch-with-streams#66.

@domenic domenic added the addition/proposal New features or enhancements label Oct 4, 2016
@domenic domenic transferred this issue from whatwg/html Aug 22, 2023
@annevk
Copy link
Member

annevk commented Aug 25, 2023

It seems this would be addressed by #48, potentially.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
addition/proposal New features or enhancements
Development

No branches or pull requests

3 participants