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

Re: [Bug 20816] "Hold" unspecified

From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Sat, 20 Apr 2013 19:43:53 +0200
Message-ID: <CALiegf=mDga0OEXxoup56Rk4mU6bwOnHW6B9BeGKkqcOkmMq0w@mail.gmail.com>
To: snandaku <snandaku@cisco.com>
Cc: piranna@gmail.com, Harald Alvestrand <harald@alvestrand.no>, public-webrtc <public-webrtc@w3.org>
I do not think that such an API funtion covers all what is requested in
this mail thread.

--
Iñaki Baz Castillo
<ibc@aliax.net>
El 20/04/2013 17:23, "Suhas Nandakumar (snandaku)" <snandaku@cisco.com>
escribió:

>  Can't directionality change be archived with existing constraint, say,
> OfferToReceiveAudio to false ...
>
>  Am I missing something here
>
> Sent from my iPad
>
> On Apr 20, 2013, at 3:42 AM, "piranna@gmail.com" <piranna@gmail.com>
> wrote:
>
>   I agree with Iñaki, I think SDP is dificult to use and overcomplicated
> from an API perspective, it should be an internal implementation detail, or
> at least WebRTC API should offer higher level functions, too.
> El 20/04/2013 11:51, "Iñaki Baz Castillo" <ibc@aliax.net> escribió:
>
>>
>> >> 3) change directionality of a stream
>> >>      sendonly, sendrecv, recvonly
>> >
>> >
>> > This requires the manipulation of an object that does not have explicit
>> representation at the current API surface.
>>
>> And that is exactly the problem and limitation. We are forced by WebRTC
>> to use SDP but we cannot play with SDP features.
>>
>> We need an API for setting  directionality of each media stream, and also
>> an API for retrieving those attibutes from a received and processed SDP.
>>
>
Received on Saturday, 20 April 2013 17:44:20 UTC

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