- From: Eric Rescorla <ekr@rtfm.com>
- Date: Mon, 18 Jun 2012 16:58:14 -0700
- To: Justin Uberti <juberti@google.com>
- Cc: "Cullen Jennings (fluffy)" <fluffy@cisco.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>
On Mon, Jun 18, 2012 at 12:22 PM, Justin Uberti <juberti@google.com> 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? This raises the question of what happens if you provide a setting that doesn't work. Do you have any way of finding out what the problem was? -Ekr
Received on Monday, 18 June 2012 23:59:23 UTC