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

Re: Additional requirement - audio-only communication

From: Harald Alvestrand <harald@alvestrand.no>
Date: Tue, 23 Aug 2011 19:18:00 +0200
Message-ID: <4E53E0C8.6010304@alvestrand.no>
To: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
CC: public-webrtc@w3.org
On 08/23/11 16:24, Stefan Håkansson LK wrote:
> On 2011-08-23 14:16, Harald Alvestrand wrote:
>
>> A18  It MUST be possible for an initiator or a responder Web application
>> to indicate the types of media he's willing to accept incoming streams
>> for when setting up a connection (audio, video, other). The types of
>> media he's willing to accept can be a subset of the types of media the
>> browser is able to accept.
> When do you think this should be indicated? I guess that in most cases 
> the establishment of a connection is foregone by some signaling (I 
> would like to communicate, would you?). Perhaps what media you would 
> be willing to receive can be agreed in this phase, and the sending 
> application would react by sending only the desired media. This way 
> there would not be a need to have specific APIs for this purpose.
I think the PeerConnection will have to be told before it sends off its 
SDP Offer.
Having properties on the PeerConnection that one can set (with default 
"audio video") is one possible API.
Received on Tuesday, 23 August 2011 17:18:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 23 August 2011 17:18:41 GMT