rptools / maptool-server-registry Goto Github PK

Is your feature request related to a problem? Please describe.
Currently a client has to chose if he wants to use webrtc or sockets to connect to a MT server. If the choice does not match with how the server is started the connection will fail after some timeout.

Describe the solution you'd like
The MT-Server should transmit all modes of connection it supports to the MT-registry. A client wanting to connect to it fetches this information, chooses the type of connection if there are more than one and connects.

Describe alternatives you've considered
Live with the status quo. But it will be more confusing if we get more options (HTTP, Websocket,...)

Is your feature request related to a problem? Please describe.
Add signalling server logic to the server registry to support RPTools/maptool#2876

Describe the solution you'd like
When the pilot/beta phase of the WebRTC connection for MapTool is completed the signalling server logic will need to be rolled into the registry.

Is your feature request related to a problem? Please describe.
Currently gm and players have to tell each other if the use webrtc or not. Because you get timeouts if you try to connect to a server with a wrong connection type.

Describe the solution you'd like
When a server starts it should submit a server type field to the registry. The clients will fetch it from there and know if they should use sockets, webrtc or something else to connect to the server. Maybe something like "supported connectiontypes" would be even better as there may be servers that allow multiple types of connections in parallel.

Describe alternatives you've considered
Just keep it as it is and tell each other if webrtc checkbox should be checked.