W3C home > Mailing lists > Public > public-webrtc@w3.org > August 2015

Proposal: Replace offerToReceiveVideo with PeerConnection.createRtpReceiver.

From: Peter Thatcher <pthatcher@google.com>
Date: Wed, 26 Aug 2015 14:54:13 -0700
Message-ID: <CAJrXDUGQ5cSg11XhGMmZe4mJsDbqQ=VgMmxi_PVGf=EPgOw=Hg@mail.gmail.com>
To: "public-webrtc@w3.org" <public-webrtc@w3.org>
It looks like we'll soon be adding PeerConnection.createRtpSender, which is
a way to create an RtpSender before one has a track to send.

The logic corollary is PeerConnection.createRtpReceiver, which would be a
way to create an RtpReceiver before any media negotiation has occurred.  In
other words, it would serve the same purpose as "offerToReceiveVideo".

In both implementing offerToReceiveVideo and using it in JS, I found it
awkward.  I think the following example code would be more natural:

var receiver = pc.createRtpReceiver("video");
// The offer now acts like it currently does with "offerToReceiveVideo = 1".
var offer = pc.createOffer();
// JS can use the receiver.track immediately.


I think this would be more natural, and more logically consistent with
PeerConnection.createRtpSender.


If you'd like to see how it would look in a PR, here it is:

https://github.com/w3c/webrtc-pc/pull/279/files
Received on Wednesday, 26 August 2015 21:55:21 UTC

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