You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WebRTCTransportProvider currently hard-wires STUN servers. People wanting to use WebRtc for transport (e.g. uProxy) would like to configure both STUN servers and employ TURN servers too (#49). These things are specific to WebRTC, so maybe don't want to be in Transport API. But we do want the option to use/specify them...
One way to do this is to make a WebRtc class that uses peer-connection and does all the work, and is configurable. Then the WebRTCTransportProvider is a lightweight wrapper around this class with some reasonable set defaults.
The text was updated successfully, but these errors were encountered:
WebRTCTransportProvider currently hard-wires STUN servers. People wanting to use WebRtc for transport (e.g. uProxy) would like to configure both STUN servers and employ TURN servers too (#49). These things are specific to WebRTC, so maybe don't want to be in Transport API. But we do want the option to use/specify them...
One way to do this is to make a WebRtc class that uses peer-connection and does all the work, and is configurable. Then the WebRTCTransportProvider is a lightweight wrapper around this class with some reasonable set defaults.
The text was updated successfully, but these errors were encountered: