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

Client mode #8

Open
seemk opened this issue Jan 4, 2018 · 2 comments
Open

Client mode #8

seemk opened this issue Jan 4, 2018 · 2 comments

Comments

@seemk
Copy link
Owner

seemk commented Jan 4, 2018

At the moment WebUDP can't initiate connections to other instances or browsers.

@notedit
Copy link

notedit commented Jan 7, 2018

cool, so webUDP will be not be only the server side. it will be webrtc datachannel peer lib.

@seeme-o
Copy link

seeme-o commented Jun 28, 2019

This may be off base, but isn't it possible to use an external agent to handle ICE/STUN/TURN as long as on the same LAN? For example, if I'm on Ubuntu running WebUDP and have standard Chrome as well (or even better node.js), what is to stop WebUDP from forwarding such events/requests to the standard WebRTC stack, then sending ICE candidates (etc) back to WebUDP. In other words, session and connection information is initiated using standard WebRTC, but passed onto WebUDP where the actual connection is created.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants