Re: RFC: Electrolysis manifesto: Chrome never blocks on content

On 4/23/10 4:52 PM, Chris Jones wrote:
> Boris Zbarsky wrote:
>> But sync means the content process can't be reentered, no? In
>> particular, within the createWindow call we currently run
>> nsFrameLoader::ReallyStartLoadingInternal, which seems to send several
>> messages to the child process. Or are those all async except the ctor
>> and therefore ok within a sync call?
>>
>
> I don't know if they're async; if they are, they're fine to send, but
> won't be processed until the 'sync' message is finished.

I think that should be fine; would need to audit the messages to be 
sure.  In particular, the race between the various loads being kicked 
off here could need resolving; that should be doable, though.

> Do the notifications being sent contain information that the content process
> can't deduce for itself?

Generally speaking, yes.  Not sure that information is relevant in this 
case.

-Boris