Short video dialogue (two speakers) explaining that a signaling server is required for WebRTC sessions: the signaling server is used to exchange the SDP offer/answer and ICE candidates. The WebRTC spec constrains the format of signaling data (SDP) but intentionally leaves the signaling transport/protocol up to implementers, so developers must provide their own signaling mechanism (e.g., a signaling server).
Do I need a signaling server?
Yes, you do. The way Web PC works is that you exchange, offer, answer, and the ICE candidates, and that's what the signaling server is for.
Okay, so wait, doesn't WebRTC comes with its own discovery, signaling, slash whatever mechanism?
No, the working group decided to explicitly limit the scope and not have the long discussion which signaling protocol is best, so you're completely on your own.
Okay, but they did decide that I'm going to use sdp, which is session description protocol. So that's signaling?
No, no, that's just the information you need to exchange. But how you exchange them is up to you.
So WebRTC works through SDP, but now it's up to me to decide how am I going to send that within the network. And that's what I need the signaling server for.
Correct?
Meta rebuilt AV1 for mobile scale. Should smaller teams follow? | Chats with Arin
