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

Re: Why is offerToReceiveAudio boolean again?

From: Taylor Brandstetter <deadbeef@google.com>
Date: Mon, 17 Apr 2017 15:12:33 -0700
Message-ID: <CAK35n0aP_2RDvJJ=2vCeqqmLEg6Ww-Da8+mVPtEbj5oxD+0i5w@mail.gmail.com>
To: Iñaki Baz Castillo <ibc@aliax.net>
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
As I recall, this decision was made because it's only being kept around as
a "legacy interface extension", and a boolean is all Chrome implemented. So
it wasn't worth the effort to specify more complex behavior (which used to
be described in JSEP, before things became transceiver-based).

On Mon, Apr 17, 2017 at 1:43 PM, Iñaki Baz Castillo <ibc@aliax.net> wrote:

> http://w3c.github.io/webrtc-pc/#configuration-data-extensions
> No longer an integer to generate N a=recvonly m= sections? Should I
> understand that addTransceiver("audio") must be used instead? If so,
> why to keep offerToReceiveAudio at all?
> --
> Iñaki Baz Castillo
> <ibc@aliax.net>
Received on Monday, 17 April 2017 22:13:06 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:18:28 UTC