Re: Necko e10s 1st cut design: slow vs premature optimization?

On Dec 4, 7:50 am, Benjamin Smedberg <[email protected]> wrote:
> On 12/4/09 10:21 AM, Jason Duell wrote:
>
> I don't think this is true, from the client's perspective. If you have a
> "fat channel", the state can safely diverge between the child and the
> parent, as long as each asynchronous message updates the state correctly.

You're right.  We're going to want an async model for performance, and
I've already started down that road, so I think I'll stay on it,
rather than open new cans o' worms.

thanks.

J