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

Re: Make MediaStream usable with postMessage

From: Anne van Kesteren <annevk@annevk.nl>
Date: Mon, 21 Oct 2013 15:14:48 +0100
Message-ID: <CADnb78ixz3y-eJ+4jKmGXTHEuBUqOtQYrRNhowT4s4vJ1UM59g@mail.gmail.com>
To: Stefan HÃ¥kansson LK <stefan.lk.hakansson@ericsson.com>
Cc: "public-media-capture@w3.org" <public-media-capture@w3.org>
On Mon, Oct 21, 2013 at 3:10 PM, Stefan HÃ¥kansson LK
<stefan.lk.hakansson@ericsson.com> wrote:
> Thanks for feedback.
> I see from the github doc that InternalStructuredClone will take a
> "targetRealm" input, and I assume you mean that we need have that
> covered in the InternalStructuredClone algorithm for MediaStream.
> Is that right?

Yeah. How exactly the extensibility hook is going to work is not
completely figured out yet. I suspect it'll take a while before this
whole thing moves to JavaScript.

> If so I guess we need to device a InternalStructuredClone algorithm that
> takes a targetRealm input. Do you see "targetRealm" coming soon, or
> would something like I proposed be sufficient for now?

It seems alright for now. Although I would encourage you to refer to
the built-in MediaStream.prototype.clone() method, so that if the
developer overrides it, you don't use that. (Alternatively define an
abstract clone operation and define clone() in terms of that. That's
what I usually do as it's somewhat clearer.)

> (Anne, sorry for spamming you, by mistake a missed the public- list in
> my first response)

It seems going via the list is faster o_O.

Received on Monday, 21 October 2013 14:15:19 UTC

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