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

Re: SDP wrapper? Object-oriented API?

From: Matthew Kaufman (SKYPE) <matthew.kaufman@skype.net>
Date: Sun, 16 Jun 2013 23:19:16 +0000
To: Iņaki Baz Castillo <ibc@aliax.net>
CC: "piranna@gmail.com" <piranna@gmail.com>, Ken Smith <smithkl42@gmail.com>, public-webrtc <public-webrtc@w3.org>, cowwoc <cowwoc@bbs.darktech.org>, "Suhas Nandakumar (snandaku)" <snandaku@cisco.com>
Message-ID: <6E2E41B8-BD08-4C5C-B1BB-73BBBD491884@skype.net>
The problem is that there is a single monolithic PeerConnection object that encapsulates several different concepts. I hear that am alternative proposal, with distinct objects and direct manipulation not tied to SDP was proposed, and y'all soundly rejected it... So I don't have much sympathy now.

Matthew Kaufman

(Sent from my iPhone)

On Jun 16, 2013, at 3:08 PM, "Iņaki Baz Castillo" <ibc@aliax.net> wrote:

> 2013/6/16 piranna@gmail.com <piranna@gmail.com>:
>> somewhere need to figure out a better way of getting these systems to
>> interoperate without arbitrary edits to of opaque text files.
>> JSON to the rescue! :-D
> JSON is not the solution-for-all. The problem of SDP is not the
> format, but its monolithic exchange (if I modify something in my local
> streams I have to send you again an entire SDP, including ICE
> information). The same would happen in a JSON version of the SDP.
> Regards.
> --
> Iņaki Baz Castillo
> <ibc@aliax.net>
Received on Sunday, 16 June 2013 23:20:44 UTC

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