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

On 4/23/10 10:27 AM, Mike Shaver wrote:

> I presume that we can't end up with a content->chrome rpc blocking the
> content process, and then the chrome process blocking because a queue
> is too full for it to post an async message to the same content
> process, right?

I believe that's correct, yes: we cache those messages in a std::vector or 
something, and should only be bounded by memory, not by any pipe-full problems.

--BDS