-
Notifications
You must be signed in to change notification settings - Fork 4
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
What's the state of WASM support? #132
Comments
WASM support is more serious than ever with my recent work on #129 which implements hard-crafted bindings to the WebTransport Web API. Also, while there are indeed no examples or readme as of now - there are tests. They are designed in such a way that we implement them once and test all the supported drivers, so both native and wasm are known to work. Another thing to note is the API currently in not stable, and I'll likely be changing the crates structure (specifically what does into the main Regarding the status of the project - it is a side project, but I am quite serious about it, as it is being used by a lot of people, including myself, in production even. The examples and proper docs are lacking due to the plans to change the Oh, and yeah, it is already being used in my own project with bevy, as well as a couple of crates that build on top of WebRTC is extremely complicated, WebTransport is much easier in this regard. They're even working on the P2P spec for it, which is super cool. Great job on Matchbox btw, I considered using it for my project before deciding on WebTransport! |
To elaborate more on the current state:
|
Is there an example of a bevy project using this, that works on WASM? Would it be much to ask for a minimum example, like bevy_rtc does? If it's stable enough I can make the switch, I will. Just trying to detect blockers. In general, im wanting to see or make a "bevy_xwt", with an exact and equivalent API to bevy_rtc. Bevy_rtc uses a server/client topology over WebRTC provided by matchbox, and hides all of the WebRTC skill gap from users, clicks into Bevy system parameters and the ecosystem, and it supports web/native. At a high level, bevy_rtc is a crate with a client and server feature (plugins), provides a "Protocol" derive macro to allow a struct to be sent/receieved, and two system parameters, RtcClient and RtcServer for reading and writing to eachother unreliable or reliable. |
This is great, as One this though - I'd like to reserve the
It sounds like the |
I'll take a look at |
I added examples |
The library seems to have no examples, tests, or a README. Is this a side project or a serious attempt at supporting WASM client webtransport in Bevy?
To add, I'm interested in seeing where this goes. I'm an author of Matchbox (WebRTC) and bevy_rtc, but I'm in the market lately for a simpler network layer. WebRTC is becoming difficult to manage.
The text was updated successfully, but these errors were encountered: