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

RE: UI Problem - media types of incoming connection

From: Jim Barnett <Jim.Barnett@genesyslab.com>
Date: Fri, 1 Jun 2012 10:14:07 -0700
Message-ID: <E17CAD772E76C742B645BD4DC602CD810649C427@NAHALD.us.int.genesyslab.com>
To: "Cullen Jennings" <fluffy@cisco.com>, <public-webrtc@w3.org>
Why not define a JS representation of the entire SDP?  With appropriate
getters and setters, it would facilitate anything that the app author
wanted to do with the SDP, including editing it before sending (which
has been mentioned several times before.)

- Jim

-----Original Message-----
From: Cullen Jennings [mailto:fluffy@cisco.com] 
Sent: Friday, June 01, 2012 12:21 PM
To: public-webrtc@w3.org
Subject: UI Problem - media types of incoming connection


Say that Alice has sent an Offer to Bob. This offer perhaps has an audio
/ video / and data stream. The JS running on Bob's browser would like to
know if this offer includes video and/or audio so that it can render an
appropriate UI. Bob might want to know if the ALice is offering video or
not before Bob decides to provide a video stream or not back to Alice. 

One option is to have the JS look at the SDP. I think we all agree this
sounds pretty gross. I'd like to propose that we add something to the
API that can take an offer and return the number of tracks of audio,
video, and data in the offer. I'm thinking something roughly like a
getCharacteristics method that takes a SessionDescription and returns a
dictionary with keys "numberAudioStreams", "numberVideoStreams",
"numberDataStreams" 

Thoughts? Sound reasonable to add something like this?
Received on Friday, 1 June 2012 17:15:39 UTC

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