-
Notifications
You must be signed in to change notification settings - Fork 33
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
Compile into .wasm #355
Comments
Is it possible for the browser to make the necessary connections to the tox network, or would it always have to pass over a server with the browser acting as a gui frontend? I know that people are working on porting libp2p to wasm, but I don't know how they plan to support tcp, udp etc connections. I thought that wasn't possible in a browser, but I might be mistaking. |
You cannot use raw tcp/udp in browser however you can use WebSockets. In Tox network there are tcp relays, we can add some code into tcp relays to accept websockets too. |
But I can't find nice solution for udp. WebRTC may not be a good solution to do this. Because it is too complex and heavy. |
You cannot use UDP in WebSockets. Tox tcp relay is designed in such a way to let users communicate with each other even without a UDP connections. |
There is a new library for unordered webRTC data channels. It's not UDP, but it's analogous. https://github.com/kyren/webrtc-unreliable |
rustwasm/gloo#49
withoutboats/romio#2
The text was updated successfully, but these errors were encountered: