W3C home > Mailing lists > Public > public-webrtc@w3.org > May 2016

Re: Rationale behind the RTCRtpTransceiver

From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Mon, 16 May 2016 16:14:38 +0200
Message-ID: <CALiegfnHzaLG=WcTzpmVYOz8TUBfKY7g_YQx_3L_Xo4FqP7JKg@mail.gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
2016-05-14 15:19 GMT+02:00 Harald Alvestrand <harald@alvestrand.no>:
>> - And here is when RTCRtpTransceiver borns. It's an artificial
>> combination of both a RTCRtpSender and a RTCRtpReceiver that share the
>> same MID (due to SDP requirements) and represents both directions of
>> the media flow within a m= section.
>
> My way of putting it: RTCRtpTransceiver is where the results of using
> SDP for negotiation are surfaced. It's a way of keeping those results
> away from RTPSender and RTPReceiver.

Clear.


>> Am I right?
>
> Read history. You may become righter.

Certainly true. Thanks a lot.


-- 
Iñaki Baz Castillo
<ibc@aliax.net>
Received on Monday, 16 May 2016 14:15:25 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:48 UTC