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

> * Channel state may change on the chrome side in ways which are inconsistent
> with what the content side expects. Once the channel is opened, are channel
> properties immutable (properties which may be get/set)? Once a channel
> closes, for example, will the header and security data still be available?

I'll have to look at the mutability/immutability of properties and how
it affects things.  But this is actually more likely to bite me if I'm
trying to keep a fat tab channel "in sync" with the chrome channel's
state.

I'm hoping that by keeping a reference to the chrome channel I can
ensure that I can keep asking it for headers, etc. after it would
normally be closed and cleaned up.  Will have to check that too.

> * Will setting a property cause side effects which might re-enter in strange ways? How will notifications (redirects, ondataavailable, etc) interact with with these synchronous IPC messages? Is it possible that an ondataavilable handler in the child (for example) might end up re-entering itself?

So all sync msgs will be from the child to the parent ("GetFoo",
etc.).  Async notifications like OnDataAvailable should just be queued
until the sync GetFoo method is complete, right?  Can you describe the
problem you're thinking of a bit more?