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

Re: UI Problem - media types of incoming connection

From: Justin Uberti <juberti@google.com>
Date: Fri, 1 Jun 2012 14:53:46 -0400
Message-ID: <CAOJ7v-1kgzdnbVkdXn6wYsXaaPkSv_TcpXgDncty1GKZ3peOgw@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
Cc: Martin Thomson <martin.thomson@gmail.com>, Cullen Jennings <fluffy@cisco.com>, public-webrtc@w3.org
I don't know if this is even needed for this case. I would think we would
handle this by calling setRemoteDescription("offer", sdp), and then look at
the MediaStream (either from remoteStreams on onaddstream to see if it has
audio or video tracks. Bob hasn't signaled anything back to Alice at this
point, so this should be fine.

Regardless, I expect we will need some sort of SDP inspection interface in
the future (see my sample where I set a=recvonly in the PRANSWER). I was
thinking that the SessionDescription object in JSEP would grow to provide
these kind of JS-friendly inspection methods.

On Fri, Jun 1, 2012 at 2:22 PM, Eric Rescorla <ekr@rtfm.com> wrote:

> On Fri, Jun 1, 2012 at 11:18 AM, Martin Thomson
> <martin.thomson@gmail.com> wrote:
> > On 1 June 2012 11:14, Eric Rescorla <ekr@rtfm.com> wrote:
> >>> Just create an answer if you wanted to show what the session could
> >>> look like.  Your choice.
> >>
> >> That only works if we have an SDP inspection interface.
> >
> > That's what Cullen was proposing, wasn't it?
> I'm not sure. I had assumed it only applied to offers.
> But I guess I would need to see a detailed API spec.
> -Ekr
Received on Friday, 1 June 2012 18:54:35 UTC

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