Re: How best to architect the InstallTrigger code to support e10s

On 3/8/10 1:07 PM, Dave Townsend wrote:

> As an overview the InstallTrigger object is what websites can use to
> test whether XPI installation is enabled and to start extension installs.
>
> The question I have is how to best restructure the code such that when
> we move to e10s full on the transition is simple. My best guess would be
> something like this:
>
> An object that implements InstallTrigger that would run in the content
> process and talks to an object in the chrome process (initially directly
> but presumably later through IPDL). From what I understand it is
> allowable for calls from the content process to the chrome process to be
> synchronous and block content, but not vice versa?

Yes. The goal would be to keep as little state in the content process as 
possible, I think: what information does the content caller get back from 
these APIs? It is a single boolean "started" or "not started" value? If so, 
we can probably just make the message a synchronous StartInstall message 
returning a single boolean value.

--BDS