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

MediaTrackConstraint structure (Re: Revised getUserMedia editor's draft available)

From: Harald Alvestrand <harald@alvestrand.no>
Date: Tue, 12 Jun 2012 07:39:20 +0200
Message-ID: <4FD6D608.3080300@alvestrand.no>
To: public-webrtc@w3.org
On 06/09/2012 03:05 AM, SUN Yang wrote:
> Hi Dan and all
>
> My question is : using MediaTrackConstrainst instead of option is for 
> what purpose?
> To my opinion, it seems make the constraint complex and more difficult 
> for understanding compared with previous edition.
>
> What's more,
> why
>
> dictionaryMediaTrackConstraints  {
>      dictionary MediaTrackConstraintSet?  mandatory  <http://dev.w3.org/2011/webrtc/editor/getusermedia.html#widl-MediaTrackConstraints-mandatory>;
>      sequence<MediaTrackConstraint>?      optional  <http://dev.w3.org/2011/webrtc/editor/getusermedia.html#widl-MediaTrackConstraints-optional>;
> };
> in MediaTrackConstraints object, the 2 parameters have different type, 
> can you telll me the real difference for these 2 parameters?I can not 
> get the meaning from the existing text?
>
This is a Media Capture TF item at the moment....

The algorithm requires that optional constraints be a sequence, so that 
the most important constraints come first.

There's no such requirement for mandatory constraints.
Received on Tuesday, 12 June 2012 05:39:50 UTC

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