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

Compile into .wasm #355

Open
kpp opened this issue Apr 4, 2019 · 5 comments
Open

Compile into .wasm #355

kpp opened this issue Apr 4, 2019 · 5 comments

Comments

@kpp
Copy link
Member

kpp commented Apr 4, 2019

rustwasm/gloo#49
withoutboats/romio#2

@najamelan
Copy link

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.

@kpp
Copy link
Member Author

kpp commented Apr 4, 2019

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.
So I believe it is possible.

@NamsooCho
Copy link
Member

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.

@kpp
Copy link
Member Author

kpp commented Apr 6, 2019

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.

@bddap
Copy link

bddap commented Apr 29, 2019

There is a new library for unordered webRTC data channels. It's not UDP, but it's analogous. https://github.com/kyren/webrtc-unreliable

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

4 participants