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

Re: Proposal: offerDataChannel in RTCOfferOptions

From: Eric Rescorla <ekr@rtfm.com>
Date: Mon, 27 Apr 2015 18:05:56 -0700
Message-ID: <CABcZeBNtRwD=WnjW5QK4nmRPH=0xsJgzFThOoCr=yo_hDVhi5w@mail.gmail.com>
To: Benjamin Schwartz <bemasc@google.com>
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
On Mon, Apr 27, 2015 at 3:01 PM, Benjamin Schwartz <bemasc@google.com>

> Currently, RTCPeerConnection has "offerToReceiveVideo" in the
> RTCOfferOptions, which is a convenience to allow creating an offer with a
> m-line for video without first having to attach a video MediaStreamTrack.
> This is useful; without it, pages would have to attach a track and then
> renegotiate, even if they only want to receive video.
> However, with data channels, we don't have this convenience.  The offerer
> must call createDataChannel before createOffer, or suffer a renegotiation,
> even if they have no immediate need for a data channel.

Why is the requirement to call createDataChannel a big deal?


> So what do you think of adding a boolean "offerDataChannel" attribute to
> RTCOfferOptions, parallel to "offerToReceive*"?  I think that would be
> easier to use.
> --Ben
Received on Tuesday, 28 April 2015 01:07:04 UTC

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