W3C home > Mailing lists > Public > public-houdini@w3.org > November 2015

Re: Isolated Script API

From: Ian Kilpatrick <ikilpatrick@google.com>
Date: Mon, 30 Nov 2015 13:00:33 -0800
Message-ID: <CAJL3UpQvTJA0T86F9AvKq+t0OAW7y3eqPvF+fVYJO+eNwEinVA@mail.gmail.com>
To: Elliott Sprehn <esprehn@chromium.org>
Cc: Chris Lilley <chris@w3.org>, "public-houdini@w3.org" <public-houdini@w3.org>
Just to follow up for those following along, we are working with the Audio
folks to see if we can use something common.

Thanks,
Ian

On Fri, Aug 14, 2015 at 5:23 PM, Elliott Sprehn <esprehn@chromium.org>
wrote:

>
>
> On Fri, Aug 14, 2015 at 5:31 AM, Chris Lilley <chris@w3.org> wrote:
>
>> Hello Ian,
>>
>> Tuesday, August 11, 2015, 2:56:12 AM, you wrote:
>>
>> > For the Houdini APIs which extend the rendering pipeline, we believe
>> > that we'll need an isolated execution environment for these APIs to
>> > be exposed in.
>>
>> I believe we will, yes. It seems safer and is probably more
>> performant, even though the main rendering thread should not be
>> blocked which removes the major perf worry.
>>
>
> This is not intended to be off main thread, just in a different context.
> In the same way that two iframes have separate scripting contexts but are
> in the same thread.
>
> Using an isolated context means the script can run directly inside
> .getBoundingClientRect() in the layout process of the engine, places where
> running script is not generally safe.
>
> - E
>
Received on Monday, 30 November 2015 21:01:02 UTC

This archive was generated by hypermail 2.3.1 : Monday, 30 November 2015 21:01:03 UTC