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

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.  Do the 
notifications being sent contain information that the content process 
can't deduce for itself?

Cheers,
Chris