- From: Cullen Jennings <fluffy@iii.ca>
- Date: Tue, 19 Jun 2012 11:03:44 -0400
- To: Justin Uberti <juberti@google.com>
- Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
On Jun 18, 2012, at 13:22 , Justin Uberti wrote: > > > On Mon, Jun 18, 2012 at 2:57 PM, Cullen Jennings (fluffy) <fluffy@cisco.com> wrote: > > This seems like good proposal, one comment on a small detail. > > On Jun 15, 2012, at 1:28 PM, Justin Uberti wrote: > >> SessionDescriptionOptions.IncludeAudio = true/false // forces m=audio line to be included >> SessionDescriptionOptions.IncludeVideo = true/false // forces m=video line to be included >> SessionDescriptionOptions.UseVoiceActivityDetection = true/false // includes CN codecs if true > > I think these three should be constraints, not settings because a given browser may not support any of them. > > > Practically speaking, what does that mean for applications? > It means they can set if theses are mandatory or optional and rate their relative importance with respect to other constraints. Some some applications might want to say, do video if you can but if you can't that is OK. Some might want to say never do video, and some might want to be able to say they need video and expect an error if that need can't be meant. All of this is exactly what constraints is good at expressing.
Received on Tuesday, 19 June 2012 17:29:12 UTC