- From: Adam Bergkvist <adam.bergkvist@ericsson.com>
- Date: Mon, 16 Sep 2013 15:32:11 +0200
- To: Martin Thomson <martin.thomson@gmail.com>
- CC: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>, Dominique Hazael-Massieux <dom@w3.org>, "public-media-capture@w3.org" <public-media-capture@w3.org>
On 2013-09-13 19:57, Martin Thomson wrote: > On 12 September 2013 22:33, Adam Bergkvist <adam.bergkvist@ericsson.com> wrote: >> In addition to transferring objects with postMessage()'s third argument, you >> can send certain objects (File, FileList, Blob, ...) as the first "message" >> argument (of type any) [1]. Objects sent that way are cloned, not >> transferred, and are still usable on the sending side after being sent. > > I guess that I could live with that, if you could convince me that > this isn't going to be a problem for people who create a MediaStream > with exclusive access to the source. We haven't enacted that > constraint yet, but it keeps coming up. From what's in the spec regarding isolated streams/tracks I can see the following options (no order of preference): 1) Not allow a stream/track with isolation constraints to be sent with postMessage(). 2) Since isolation, according to the spec, is about limiting the use of a track to rendering and sending it to a specified peer, the same rules could apply at the receiver. A step further would be to only allow rendering. /Adam
Received on Monday, 16 September 2013 13:32:41 UTC