I agree. No use-case should require developers to modify or parse SDP directly. Ideally SDP manipulation should be implementation detail hidden behind an API. Gili On 20/04/2013 6:40 AM, 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 > <mailto: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 19:44:55 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:17:42 UTC