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

WebTransport support #212

Open
1 of 6 tasks
FZambia opened this issue Nov 19, 2021 · 1 comment
Open
1 of 6 tasks

WebTransport support #212

FZambia opened this issue Nov 19, 2021 · 1 comment

Comments

@FZambia
Copy link
Member

FZambia commented Nov 19, 2021

An issue to track WebTransport support:

  • Make a POC based on quic-go Webtransport pull request
  • Make sure Disconnect logic matches ours (i.e. WT can be closed with code and string reason)
  • Add StreamCommandDecoder which accepts io.Reader and exposes Commands
  • Modify DataEncoder to always append \n to JSON, for single WebSocket messages we have fast path which does not use DataEncoder – so for single messages \n won't be included into payload sent.
  • Expose handleCommand to Client's public API. Maybe remove Client.Handle and move command decoding to Transport.
  • With the base above introduce an example with NewWebtransportHandler and WebtransportConfig which uses quic-go for WT stuff.
@FZambia
Copy link
Member Author

FZambia commented Jul 21, 2022

We experimentally support WebTransport in Centrifugo now. The code is here: https://github.com/centrifugal/centrifugo/tree/master/internal/wt.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant