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

problem with constraints algorithm

From: Cullen Jennings (fluffy) <fluffy@cisco.com>
Date: Tue, 10 Jul 2012 20:16:06 +0000
To: "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <B5BFF7C1-7FC7-4FAA-9150-3182FFE9D424@cisco.com>

It currently says 

4 Let the secondPassSet be the current contents of the candidateSet.

5  For each constraint key-value pair in the "optional" sequence of the constraints that are for the current media type, in order,

	1  If the constraint is not supported by the browser, skip it and continue with the next constraint.

	2  Remove from the secondPassSet any tracks that cannot satisfy the value given for the constraint.

	3  If the secondPassSet is now empty, let the secondPassSet be the current contents of the candidateSet. Otherwise, let the candidateSet be the current contents of the secondPassSet.




But in 5.3, I think it should go back to what it was before 5.2 not what it was in step 5. Think of the case where an earlier constraint removed some but not all of the tracks. Then a later constraint removed all the tracks - it's the effect of the last constrains that we want to roll back. 

If this does not make sense, I provide a more detailed example. 
Received on Tuesday, 10 July 2012 20:16:38 UTC

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