-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Peerjs broker protocol #48
Comments
@metzlar Its be a very long time since the original issue was created. I came across a similar use case. Has anyone worked on a python peerjs client yet? Happy to help. |
It's not our priority at all to have different language clients. If you want a server + you know javascript = just use nodejs |
I just realized that this issue was open under peerjs-server. I agree with your point on server side. For the client side, I see potential for enabling clients/peers from various languages (IoT, mobile) to connect easily. Just FYI, I started working on a python port. |
Close issue because no activity. |
Hi Peerjs team!
To test a client browser's compatibility, I'm writing a Python peerjs client. Consider this flow:
Client browser creates a new peer:
peer = new Peer('', {options});
Client posts peer info to web server:
xhr('/some-url', {peer-info})
Server uses Python peerjs client to create a p2p connection and send the Client browser a message.
I know peerjs is meant for browser p2p RTC but me thinks a python client (just the brokering) might be helpful for testing a client's capabilities? I don't need help on the actual webRTC protocol just communicating with the peerjs server to connect to the browser. If someone could point me to the right direction? Thanks!
The text was updated successfully, but these errors were encountered: