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

Re: Spec question: Using settings dictionaries instead of MediaConstraints ([ACTION-50])

From: Cullen Jennings <fluffy@iii.ca>
Date: Thu, 21 Jun 2012 18:40:08 -0400
Cc: Justin Uberti <juberti@google.com>, public-webrtc@w3.org, Eric Rescorla <ekr@rtfm.com>
Message-Id: <1AF2ECBA-D3F7-4BE1-AAC5-9B08D5722C7F@iii.ca>
To: Adam Bergkvist <adam.bergkvist@ericsson.com>

On Jun 18, 2012, at 19:53 , Eric Rescorla wrote:

>>> 
>>> This results in new dictionaries IceOptions and
>>> SessionDescriptionOptions, with values as shown below:
>>> 
>>> IceOptions.AllowedCandidates = ("none", "relay", "all) // "all", if not
>>> specified
>>> 
>>> SessionDescriptionOptions.IncludeAudio = true/false // forces m=audio
>>> line to be included
>>> SessionDescriptionOptions.IncludeVideo = true/false // forces m=video
>>> line to be included
> 
> By "forces" you mean "even if I don't include a video stream"?
> That's what I'm taking from Adam's comment.
> What happens if I AddStream() a video stream  but set this to
> false?
> 
> Maybe it would make more sense to have this *only* control
> generating a recv-type media stream and have addstream
> control only a send-type.

I'd much prefer using the terminology that is currently defined in the spec for constraints to do this which is 

OfferToReceiveVideo

and not IncludeVideo

Have a read of section 5.1
Received on Friday, 22 June 2012 01:05:20 UTC

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