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

Re: Proposal: offerDataChannel in RTCOfferOptions

From: Justin Uberti <juberti@google.com>
Date: Tue, 28 Apr 2015 17:03:41 -0700
Message-ID: <CAOJ7v-0oCRk-wLBdr6u4hcTb7Rg2LT=nW=5NVjP0ByQkskjGCQ@mail.gmail.com>
To: Peter Thatcher <pthatcher@google.com>
Cc: Martin Thomson <martin.thomson@gmail.com>, Benjamin Schwartz <bemasc@google.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>
On Tue, Apr 28, 2015 at 9:35 AM, Peter Thatcher <pthatcher@google.com>
wrote:

> On Tue, Apr 28, 2015 at 9:18 AM, Martin Thomson <martin.thomson@gmail.com>
> wrote:
>
>> What is the material difference between:
>>
>> var pc = new RTCPeerConnection({yesIWantADataChannel: true});
>> negotiate(pc).then(_ => {
>>    var dc = pc.createDataChannel();
>>    useDataChannel(dc);
>> });
>>
>> ...and:
>>
>> var pc = new RTCPeerConnection();
>> var dc = pc.createDataChannel();
>> negotiate(pc).then(_ => {
>>    useDataChannel(dc);
>> });
>>
>> Both require that you do something before negotiating.
>>
>>
> ​The second leads to more confusion, and least judging by how many people
> come to be me confused.
>
>
>
>> If the suggestion were to have a data channel created by default, with
>> an option instead to suppress that behaviour; *that( I might be able
>> to understand.
>>
>>
> ​I'd be even more happy if "offerDataChannel" were true by default, just
> like "offerToReceiveAudio" is. ​
>

This is a bit too far. Since the default bundle policy is balanced, having
this be true by default will have additional transport costs to existing
applications.

FWIW, offerToReceiveAudio is 0 by default, unless you have attached an
audio track.
Received on Wednesday, 29 April 2015 00:04:29 UTC

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