← View all posts
APRIL 4, 2018
Contributed by Jan-Ivar Bruaroey,
Firefox now implements the RTCRtpTransceiver API, a.k.a. stage 3 in my blog post “The evolution of WebRTC 1.0.” from last year.
Transceivers more accurately reflect the SDP-rooted network behaviors of an RTCPeerConnection.
E.g. addTransceiver() (or addTrack) now creates a receiver at the same time, which correlates better with the bi-directional m-line that begins life in the SDP offer, rather than being something that arrives later once negotiation completes. This lets media arrive early on renegotiation.
But most WebRTC sites today are still written the old way, and there are subtle differences to trip over. Web developers