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: Sat, 14 May 2016 00:37:22 +0200
Message-ID: <CALiegfk2Q0ssmhrixwRxM7PyVqMNxE4BAxayLSwGbNx9Tyr0kg@mail.gmail.com>
To: Peter Thatcher <pthatcher@google.com>
Cc: Taylor Brandstetter <deadbeef@google.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>
2016-05-13 22:31 GMT+02:00 Peter Thatcher <pthatcher@google.com>:
> You are correct.  ORTC does not need an RtpTransceiver, and we's carefully
> designed the RtpTransceiver to contain all of the SDP cruft so that
> RtpSender/RtpReceiver don't.  You can think of RtpTransceiver as
> RtpSdpMediaSection, because that's kind of what it is.  When using ORTC (or,
> hopefully, WebRTC NV), you can just ignore the RtpTransceiver.

Thanks to both. Very constructive.


-- 
Iñaki Baz Castillo
<ibc@aliax.net>
Received on Friday, 13 May 2016 22:38:11 UTC

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