Re: New Editor's draft (v20140321)

Regarding nativeSettings, see http://lists.w3.org/Archives/Public/public-media-capture/2013Oct/0136.html.

This was proposed on the list, only Martin commented.  It has taken this long to get into the spec because we needed to finish constraint changes first.

-- dan

On Mar 21, 2014, at 10:37 AM, Jan-Ivar Bruaroey wrote:

> On 3/21/14 9:07 AM, Adam Bergkvist wrote:
>> Hi 
>> 
>> A new version of the editor's draft is available. 
>> 
>> Dated version: http://dev.w3.org/2011/webrtc/editor/archives/20140321/getusermedia.html 
>> Living document: http://dev.w3.org/2011/webrtc/editor/getusermedia.html 
>> 
>> Changes include: 
>> 
>>     Bug 24928: Remove MediaStream state check from addTrack() algorithm. 
>>     Bug 24930: Remove MediaStream state check from the removeTrack() algorithm. 
> 
> Thanks!
> 
>>     Added native settings to tracks. 
> 
> Use-case please? Where was this discussed? It is unclear what this is intended to solve.
> 
> Looking at the language for  getNativeSettings(), I have concerns about this API: " Note that both the track settings and the native settings are snapshots and can change without application involvement."
> 
> Native settings that can change. Are we supposed to poll reactively for changes to "native" settings after we've already gotten the wrong thing? That seems awfully late. I would think that what's native about any source (or anything) would be almost entirely deterministic, and discoverable ahead of time, with something like getCapabilities().
> 
> So if anything, I think we're extending in the wrong place here.
> 
> I am, however, impressed by how this got in here so expediently. ;-)
> 
>>     Removed videoMediaStreamTrack and audioMediaStreamTrack since they are no longer necessary. 
>> 
>> 
>> Please review and provide feedback. 
>> 
>> Adam (for the editors) 
> 
> .: Jan-Ivar :.
>