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

Signalling server #2

Open
msj121 opened this issue Jun 30, 2016 · 2 comments
Open

Signalling server #2

msj121 opened this issue Jun 30, 2016 · 2 comments

Comments

@msj121
Copy link

msj121 commented Jun 30, 2016

A feature request to show how to use socket.io for signalling. I see you mention using it, but the code uses the default server.

@dnish
Copy link
Owner

dnish commented Jun 30, 2016

On your server:

git clone https://github.com/muaz-khan/RTCMultiConnection.git

...and then you can do

node server.js

This will start your own socket.io server for RTCMultiConnection.

@msj121
Copy link
Author

msj121 commented Jun 30, 2016

Oh so nothing in meteor then? Interesting. Run it outside of meteor?

Thanks.

Last question. Some of rtcMulticonndction examples (simple etc..) just include the rtcmulticonnection.js as a JavaScript external source file and still open and connect with it. Is there a reason to go through all of the headache of making a package and importing etc... Instead of just using a cdn link? Easier to update code version I guess.

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

2 participants