Re: Why is offerToReceiveAudio boolean again?

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>
>
>