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

Re: Why is offerToReceiveAudio boolean again?

From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Tue, 18 Apr 2017 10:50:47 +0200
Message-ID: <CALiegfkGydoKggEZ64S6W4mA09krZHjUF=H5ugBs4GzzA5i0iQ@mail.gmail.com>
To: Taylor Brandstetter <deadbeef@google.com>
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
2017-04-18 0:12 GMT+02:00 Taylor Brandstetter <deadbeef@google.com>:
> 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).

Well, Firefox does it well (offerToReceiveAudio:5 creates 5 m=audio
recvonly sections). I understand it should be deprecated (and
removed), but still don't understand why to come back to a previos
spec...


-- 
Iñaki Baz Castillo
<ibc@aliax.net>
Received on Tuesday, 18 April 2017 08:51:41 UTC

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