-
Notifications
You must be signed in to change notification settings - Fork 79
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 backend #251
Comments
Thanks for bringing the If this were to develop to the point of a standard - and be available through In the interest of tempering expectations, is not nearly at that stage yet and it's possible possible @johanhelsing and @simbleau will have other thoughts |
Yea no worries, I understand QUIC is still in early adoption phase, and it might not end up fitting into Matchbox. But thank you for considering it! Either way, I still plan on using Matchbox for my game, and I just figured I'd raise the issue to learn what (if any) long term plans there were. |
I haven't looked into QUIC yet much at all, so I googled compatibility with WASM. At the moment, not a shot. Solely because Safari doesn't support this In the future when it has full adoption, it sounds good on paper. I haven't looked into specifics. |
@johanhelsing Imo any experimental backends like webtransport or QUIC would warrant a new crate. I think this crate is focused on webRtc and will remain that way, since it's embedded too deep to change at this point. Thoughts? I think we should close as "won't do." |
I'm just curious if there is interest in implementing a WebTransport (QUIC) "backend" for the peer-to-peer connections.
There is a relatively new crate for using the WebTransport protocol: https://github.com/BiagioFesta/wtransport
I can see that Matchbox is specifically designed for peer-to-peer networking, relying on a relay server to set up the mesh. I'm not sure if setting up a P2P WebTransport connection is possible or easy at the moment, but I know there are efforts to do so.
Anyway, I need to read more of the code to see what's possible, but I figured I'd start this conversation early.
The text was updated successfully, but these errors were encountered: