Re: SDP wrapper? Object-oriented API?

I know what you said, but was just that "modularity" why it was so much
opposed, why I believe the (alternative) SDP mechanism is not tied to how
modular other parts are...
El 17/06/2013 01:20, "Matthew Kaufman (SKYPE)" <matthew.kaufman@skype.net>
escribió:

> 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>
> >
>