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

Re: Spec question: Using settings dictionaries instead of MediaConstraints

From: Justin Uberti <juberti@google.com>
Date: Mon, 18 Jun 2012 21:49:46 -0400
Message-ID: <CAOJ7v-1fM3vtjfpH8OCKU6LznJgREDsdWER_y+MM-sOGwdqOHw@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
Cc: "Cullen Jennings (fluffy)" <fluffy@cisco.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>
On Mon, Jun 18, 2012 at 7:58 PM, Eric Rescorla <ekr@rtfm.com> wrote:

> 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?
>

Not really; I suspect you would probably have to enum the capabilities if
you wanted to make sure your app worked properly in all cases.


>
> -Ekr
>
Received on Tuesday, 19 June 2012 01:50:35 UTC

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