- From: Rob Manson <roBman@buildAR.com>
- Date: Sat, 01 Nov 2014 10:38:18 +1100
- To: "public-media-capture@w3.org" <public-media-capture@w3.org>
Hi, in "5. The model: sources, sinks, constraints, and settings "[1] there is a brief statement about remote stream and constraints. "...though in this specification sources with the remote||||attribute set to true do not consider the current constraints applied to a track)." My question is, do the ConstrainablePattern components (e.g. Settings, etc.) get transferred through an RTCPeerConnection so that on the client the remote MST has access to them? My first thought is that this has to be no, otherwise there would be obvious fingerprinting and privacy issues. Obviously some values are available by default because they are just meta data about the structure of the stream and could be accessed through the HTMLVideoElement (e.g. videoWidth). If the answer is no, then I think we should be much more explicit in the comment I reference above. And I'm not sure from reading the spec how/where it would make it clear that MediaStreamTracks with remote == true should not support getCapabilities/getConstraints/getSettings/... If I've missed where this is defined (perhaps relative to another spec/draft) then please point me in the right direction. Thanks. roBman [1] http://w3c.github.io/mediacapture-main/#the-model-sources-sinks-constraints-and-settings
Received on Friday, 31 October 2014 23:31:50 UTC