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

Re: SDP wrapper? Object-oriented API?

From: Roman Shpount <roman@telurix.com>
Date: Wed, 19 Jun 2013 11:09:47 -0400
Message-ID: <CAD5OKxv7uN8vQaiu6oo0WfSoKGLwTYB0AFXQcSq5BM4Xkvo==A@mail.gmail.com>
To: cowwoc <cowwoc@bbs.darktech.org>
Cc: Iñaki Baz Castillo <ibc@aliax.net>, piranna@gmail.com, Frédéric Luart <frederic.luart@apizee.com>, public-webrtc@w3.org, Silvia Pfeiffer <silviapfeiffer1@gmail.com>
On Wed, Jun 19, 2013 at 10:58 AM, cowwoc <cowwoc@bbs.darktech.org> wrote:

>     That's fine and well but you've got to start somewhere. What's the
> harm in collecting use-cases and building an API on top of SDP for now?
> Even if you're right, it's hard to convince people to make such a large
> leap at once. Let's see what this API ends up looking like, and we can then
> revisit the idea of taking it to a higher level.
>     Long term, you will need to come up with a *concrete* proposal for an
> API that works for signaling protocols that require Offer/Answer and yet
> doesn't expose those details to end-users. Like I said, let's start small
> and build up to these goals.
I would argue that this is a waste of time since we need to decouple
current peer connection object, not change the object passed to it. Putting
object wrapper on SDP will get us nowhere.
Roman Shpount
Received on Wednesday, 19 June 2013 15:10:19 UTC

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