These are chat archives for andyet/SimpleWebRTC

24th
Mar 2017
Serge
@herkyl
Mar 24 2017 17:54
Hello, anyone here?
Tobias Steinmann
@tobiasps
Mar 24 2017 18:08
I'm here ;)
Serge
@herkyl
Mar 24 2017 18:08
Hey Tobias
I am trying to write my own adapter instead of socket.io and am quite confused
I got it to send out the "join" event to join a channel, however the callback I provide is invalid since it doesn't have the correct clients hash
I see that the client hash has properties like "screen", "audio" & "video", where are they set for each user? There is no message in network traffic that would tell that
I might be overthinking something
Tobias Steinmann
@tobiasps
Mar 24 2017 18:16
I'm fairly new to WebRTC and SimpleWebRTC, so I may not be able to help. You are trying to replace the signaling server and/or just the socket.io client?
Serge
@herkyl
Mar 24 2017 18:16
I am trying to replace Socket.io client with Scaledrone.com client
Tobias Steinmann
@tobiasps
Mar 24 2017 18:17
And still using the Signalmaster (based on socket.io) signaling server.
Serge
@herkyl
Mar 24 2017 18:17
hmm
I have not done anything to not use it, how is it used, I don't see it in package.json
Tobias Steinmann
@tobiasps
Mar 24 2017 18:19
There's some information sharing going on in the signal server. Stuff like when you send join message it tells responds who is in the room and lets the others know you have joined.
Serge
@herkyl
Mar 24 2017 18:19
ok, so there is also a custom server part for SimpleWebRTC
Tobias Steinmann
@tobiasps
Mar 24 2017 18:19
Yes
Serge
@herkyl
Mar 24 2017 18:19
oh
I thought all data does client to client tbh
thanks for clarifying
Serge
@herkyl
Mar 24 2017 18:20
mhm
I see
thanks! :)
Tobias Steinmann
@tobiasps
Mar 24 2017 18:20
Your welcome :)
Serge
@herkyl
Mar 24 2017 18:20
If I wanted to not use it, could I do that?
just follow similar API as it on my own I guess
Tobias Steinmann
@tobiasps
Mar 24 2017 18:21
Yes. It runs in node.js.
Yes it is not that complicated, so you could replace it with something else.
Be aware that browsers now require https for WebRTC, so you need to enable SSL for Signalmaster or your own signal server.
Serge
@herkyl
Mar 24 2017 18:22
mhm
thanks
Tobias Steinmann
@tobiasps
Mar 24 2017 18:23
Luckily that accept selfsigned certificates :)
You also need to get you head around STUN and TURN servers. They are needed to allow the peers to connect through NAT and firewalls. SimpleWebRTC defaults to Google STUN, but no TURN, this you also need to setup yourself.