WebSocket / WebRTC about webrtc-example HOT 3 CLOSED

Yes, that's correct. Websockets are client-to-server while webrtc is client-to-client (or client-to-server if using a TURN server).

from webrtc-example.

I am not a networking expert, but client x client / client x server seems irrelevant to me. If i understand correctly the nature of communication the main difference of TCP & UDP:
UDP - does not expect response, lost packets aren't resent
results in lower com. delays, suitable for live streams, high tick-rate game communication, definitely not suitable for integrity sensitive data (for example online game movement is suitable to be communicated via UDP | login to hive server, items transactions via TCP)
TCP - generally commoner, expects response, a bit higher com. delay, lost packets are resent

Therefore I believe WebRTC and WebSockets are suitable for different cases.

from webrtc-example.

The difference between the two is more than just TCP vs UDP. They're different protocols designed for different use cases.

from webrtc-example.