-
Notifications
You must be signed in to change notification settings - Fork 355
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
WebTransport: Add WebTransport as a new transport #703
Comments
Hi! @thernstig ! This is indeed on our radar. Adding this transport on the client-side should be quite straightforward, but the server will require a bit more work. Related:
|
@darrachequesne that is great. I could not find an issue, hence why I created one. Looking forward to it in the future! |
Now if only Safari could get with the program: https://caniuse.com/webtransport |
Is your feature request related to a problem? Please describe.
WebTransport (https://developer.mozilla.org/en-US/docs/Web/API/WebTransport) is a new HTTP/3 protocol that promises even faster connection time and solving various issues with WebSockets.
It would be cool if socket.io could transparently start implementing
webtransport
as a new transport option. Still keeping the same nice fallback mechanism that exists today between WebSockets and HTTP long-polling.Describe the solution you'd like
Add a new
transports
option useable in client initialization: https://socket.io/docs/v3/client-initialization/#transportsDescribe alternatives you've considered
Using WebTransport directly without socket.io. But that completely misses the cool API that socket.io provides.
The text was updated successfully, but these errors were encountered: