On Oct 16, 2014, at 5:31 PM, Boris Zbarsky wrote:

> On 10/16/14, 5:58 PM, Brendan Eich wrote:
>> Can you say more?
> 
> Vats as currently specified have independent event loops and allow parallel 
> JS execution, in the sense that they are totally disconnected from each other 
> and have separate run-to-completion guarantees.
> 
> A window and its same-origin subframe have two separate WindowProxys but 
> can't really be separate Vats given the above, yes?

We've also talked about this in the other recent related thread.

As Vats are current specified (the ES6 spec essentially describes a single 
Vat), the host is responsible for making Job scheduling decisions for each Vat. 
 This means that a host that is managing multiple Vats could impose a 
synchronous scheduling policy that spans multiple Vats. This seems like it may 
be sufficient to describe browsers behavior.

Allen

_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss

Reply via email to