-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
QUIC support #3769
Comments
That would be awesome indeed 👍 Related: |
Bad news:
Good news:
|
@darrachequesne just checking in — any new developments on the node support side (two years later)? |
@reececomo it's coming: https://github.com/socketio/engine.io/releases/tag/6.5.0 We'll use the |
WebTransport is now supported: https://github.com/socketio/socket.io/releases/tag/4.7.0 We'll add a guide to test it with a self-signed certificate in local environments (soon). |
Nice one @darrachequesne! |
The guide: https://socket.io/get-started/webtransport Any feedback is welcome! |
That is awesome, great job! Currently we're using geckos.io (WebRTC datachannel), and interested to see if QUIC/webtransport offers any performance improvement/reduces packet overhead. |
Might be interesting to see a side-by-side comparison between websockets and webtransport with a realtime game/sim (i.e. like @yandeu's here: https://www.youtube.com/watch?v=ZEEBsq3eQmg) |
Awesome! Is it possible/planned to use datagrams instead of streams? |
Interestingly Desktop Safari and a handful of mobile browsers say they support QUIC (HTTP/3) but not Webtransport. Not fully across the particulars here, we'll continue with WebRTC data channels in the meantime. |
@reececomo i find it importent to point that out i also go at present for everything with webrtc directly i ship only the inital html |
It would be super awesome if socket.io can use QUIC as one of its transport layers.
The text was updated successfully, but these errors were encountered: