Re: Cross-process JS wrappers

On 8/31/09 11:12 AM, Boris Zbarsky wrote:

> Right; hence the need for a notification when the listener is entered
> too, per what I said.

I misinterpreted. Maintaining that stack sounds like a lot of trouble...
let's wait and see whether we actually need to.

>>> The hard part is what happens if the script spins the event loop.  ;)
>>
>> If the script spins the event loop it doesn't have any useful atomic
>> run-to-completion semantics anyway, right?
> 
> It does from start to when it starts spinning and from when it stops
> spinning to end....

Sure, but I think the original proposal would have taken care of that: you
lock when you first create/use a JPW, it auto-unlocks when the event loop
spins, and it would re-lock when you create/use a JPW after you return from
the event loop.

--BDS