Short transcript of a two-person technical discussion (YouTube) about when to choose a proprietary signaling protocol versus reusing an existing one. Speaker B advises: prefer using the signaling system already present in your stack (e.g., SIP/XMPP/jingle), otherwise implement a JSON/JSEP-style approach or a proprietary/open-source framework — choice depends on existing system integration and developer preferences.
When is it best to choose a proprietary signaling protocol?
This has been our favorite battle for the last 10 years. WBRC does not define the signaling protocol, so you're on your own. You can use an existing standard protocol like SIP or XMPP's Django protocol, or you just do this JavaScript session JSEP session establishment protocol, which is the ITF standard for Percy. It's an abstract signaling protocol and basically that's just okay. We are sending these JSON things we get from the API around.
Okay, but which one is the best one for us?
It mainly depends on what your existing system does. If you have one, if you have one. For example, if you have a chat system that uses XMVP or something like that, then go for jingles there if you're building something new. JSON is what people favor these days.
So assuming I have one that is already there, I would use that. Otherwise I would build my own, which is going to be probably either proprietary or whatever that open source framework that I chose. Use for me. Uses for me.
Yes.
Okay, thank you.
Meta rebuilt AV1 for mobile scale. Should smaller teams follow? | Chats with Arin
