Add WebRTC Signalling server logic about maptool-server-registry HOT 3 OPEN

I think we should also store a server type in the server registry. The player connecting to a server shouldn't have to know if he has to use WebRTC or not. This information should come from the registry. Anticipating more server types in the future it should be an enum an not a IsWebRTC bool IMO.

from maptool-server-registry.

I think we should also store a server type in the server registry. The player connecting to a server shouldn't have to know if he has to use WebRTC or not. This information should come from the registry. Anticipating more server types in the future it should be an enum an not a IsWebRTC bool IMO.

I agree, at the moment the server registry is completely unaware this is going on but when when we add the WebRTC signalling support to it then we can remove the use WebRTC checkbox from the connect to server dialog and have the client retrieve that information from the registry.

from maptool-server-registry.

We probably also need a TURN server for webRTC. TURN-servers require authentication. I think it would be a bad idea to put credentials for our TURN server in the source code because other people will probably use up our traffic.

coturn can be configured to use a mysql backend. How about we add the coturn tables to our db and add secrets an allowed ips for users during the signaling process.

So it would work like:

from maptool-server-registry.