- From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
- Date: Wed, 11 Sep 2013 12:50:31 +0000
- To: Harald Alvestrand <harald@alvestrand.no>
- CC: "public-media-capture@w3.org" <public-media-capture@w3.org>
On 2013-09-11 14:31, Harald Alvestrand wrote: > Changing the subject, since this is not about createObjectURL any more.. > > On 09/10/2013 06:47 PM, Martin Thomson wrote: >> >> If you want to invent new mechanisms, another way of thinking of this >> would be to create an RTCSelfConnection that worked like >> RTCPeerConnection. You could instantiate one in each window and pipe >> the output from window to another. >> > In fact you can already do that today with a regular PeerConnection > (albeit with a somewhat inefficient coupling mechanism: encode/decode > and UDP over the local interface). If it turns out to be an often needed > use case, it should be easy to define rules that allow the UA to > discover that it's in a special-case state and can use more efficient > transfer mechanisms. I was thinking the same, but OTOH postMessage is already available in the web toolbox and we would "just" have to define how a MediaStream is either "structurally cloned" (which is what Adam proposed IIUC) or transferred. > > > >
Received on Wednesday, 11 September 2013 12:50:56 UTC