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

Feature Request: WebTransport Support #3166

Open
ALPSMAC opened this issue Nov 18, 2024 · 0 comments
Open

Feature Request: WebTransport Support #3166

ALPSMAC opened this issue Nov 18, 2024 · 0 comments
Labels
Status: Available No one has claimed responsibility for resolving this issue.

Comments

@ALPSMAC
Copy link

ALPSMAC commented Nov 18, 2024

I recently ran across the up-and-coming browser standard WebTransport ( https://caniuse.com/?search=WebTransport ) which has some performance benefits over WebSocket, at least in cases where http3 is available.

To the best of my knowledge there's no normative support for WebTransport yet in any MQTT version specification and browser support for WebTransport is still spotty. It's also not clear to me to what extent MQTT's inherent QoS and protocol specification would benefit from WebTransport.

That said, a quick search in the GitHub issues for Mosquitto didn't reveal any open issue about WebTransport, so I figured I'd at least raise the possibility for support. This might be a long way off, but it does look like there's at least some cxx support out there for WebTransport now ( https://github.com/libp2p/cpp-libp2p | https://docs.libp2p.io/concepts/transports/webtransport/ ) that might make integration easier.

Not sure if Mosquitto has an official feature backlog somewhere that might be better suited for this request, or if it would be better to make a proposal to the upstream MQTT specification... if so, my apologies for the issue spam. Just wanted to get the idea on the project's radar... Thanks!

Kind Regards,
Andy

@github-actions github-actions bot added the Status: Available No one has claimed responsibility for resolving this issue. label Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Available No one has claimed responsibility for resolving this issue.
Projects
None yet
Development

No branches or pull requests

1 participant