W3C home > Mailing lists > Public > public-media-capture@w3.org > May 2013

RE: questions about direct assignment

From: Jim Barnett <Jim.Barnett@genesyslab.com>
Date: Thu, 30 May 2013 01:18:28 +0000
To: "robert@ocallahan.org" <robert@ocallahan.org>, Martin Thomson <martin.thomson@gmail.com>
CC: "public-media-capture@w3.org" <public-media-capture@w3.org>
Message-ID: <57A15FAF9E58F841B2B1651FFE16D281042487@GENSJZMBX02.msg.int.genesyslab.com>
So is it the case that:

1.       By default, the origin of the MediaStream is the origin of the page that requested it.

2.       If the noaccess constraint is set, the origin of the page is a nonce URL not shared with any other page.

3.       If the peerIdentity constraint is set, the origin of the page is the origin/URL of the specified peer.

4.       Unlike at least some other constraints, the origin of a MediaStream cannot be changed by applying further constraints.

If 1-4 are true, I’m still not sure how this works in practice.  Constraints are set by the JS code.  So to set the noaccess constraint, the JS code has to (in effect) say: I want a MediaStream and I promise not to touch it.  But shouldn’t the user have the option of saying, whenever the JS code requests a  MediaStream: you can have a device/Track, but you can’t access it?  Can the user’s response to gUM add extra constraints?  (And if so, we have to change the constraint algorithm, because if the JS asks for an unconstrained stream,  and the user restricts it to noaccess, the obvious result is an over-constrained error.)


-          Jim

From: rocallahan@gmail.com [mailto:rocallahan@gmail.com] On Behalf Of Robert O'Callahan
Sent: Wednesday, May 29, 2013 6:32 PM
To: Martin Thomson
Cc: Jim Barnett; public-media-capture@w3.org
Subject: Re: questions about direct assignment

On Thu, May 30, 2013 at 10:23 AM, Martin Thomson <martin.thomson@gmail.com<mailto:martin.thomson@gmail.com>> wrote:
On 29 May 2013 14:48, Robert O'Callahan <robert@ocallahan.org<mailto:robert@ocallahan.org>> wrote:
> For gUM, the origin of the MediaStream should be the origin of the page that
> requested it.
That is only true when the peerIdentity or noaccess constraints are
not in place.  Those constraints change the origin.  (Though to be
fair, that's also in the WebRTC spec.)

Sure, as long as the origin is properly specified somewhere.

Rob
--
q“qIqfq qyqoquq qlqoqvqeq qtqhqoqsqeq qwqhqoq qlqoqvqeq qyqoquq,q qwqhqaqtq qcqrqeqdqiqtq qiqsq qtqhqaqtq qtqoq qyqoquq?q qEqvqeqnq qsqiqnqnqeqrqsq qlqoqvqeq qtqhqoqsqeq qwqhqoq qlqoqvqeq qtqhqeqmq.q qAqnqdq qiqfq qyqoquq qdqoq qgqoqoqdq qtqoq qtqhqoqsqeq qwqhqoq qaqrqeq qgqoqoqdq qtqoq qyqoquq,q qwqhqaqtq qcqrqeqdqiqtq qiqsq qtqhqaqtq qtqoq qyqoquq?q qEqvqeqnq qsqiqnqnqeqrqsq qdqoq qtqhqaqtq.q"
Received on Thursday, 30 May 2013 01:19:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:26:17 UTC