Re: Why is offerToReceiveAudio boolean again?

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