W3C home > Mailing lists > Public > public-webrtc@w3.org > August 2012

Re: Microsoft API Proposal

From: Martin Thomson <martin.thomson@gmail.com>
Date: Thu, 9 Aug 2012 08:43:33 -0700
Message-ID: <CABkgnnVDupKwONFeWbk=ATPs5+z4oicdp0oc0HJM2yDRT2HR-w@mail.gmail.com>
To: Jim Barnett <Jim.Barnett@genesyslab.com>
Cc: Stefan Hakansson LK <stefan.lk.hakansson@ericsson.com>, public-webrtc@w3.org
On 7 August 2012 10:37, Jim Barnett <Jim.Barnett@genesyslab.com> wrote:
> On the issue of replacing SDP, I'm trying to understand how the RealTimeMedia description would be signaled between the peers.  Examples 1 and 2 in Section 2 show side A calling:
>   signalingChannel.send(description.toDictionary());
>
> Then on the receiving side B we have:
>  function receiveDescriptionFromSignaling(remoteDescription) {.....
>
> So it appears that something on side B had to receive the message, recognize that it was a RealTimeMediaDictionary, build the appropriate structure, and then call receiveDescriptionFromSignalling.  Is the browser supposed to do this?  How would the two ends agree on the signaling protocol?  I thought that the point of SDP was to solve this kind of problem.  You may have a better solution in mind, but I haven't been able to figure out what it is.

Sorry for missing this in the flood.  SDP does not solve the problem
of how the signaling channel is built.  That is always the
application's problem.  JSEP still requires all these actions to occur
in much the same way.  In this regard, both specifications are
essentially identical.
Received on Thursday, 9 August 2012 15:44:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 9 August 2012 15:44:06 GMT