[whatwg] Worker feedback
robert at ocallahan.org
Mon Apr 6 19:17:33 PDT 2009
On Tue, Apr 7, 2009 at 5:04 AM, Michael Nordman <michaeln at google.com> wrote:
> There are additional constraints that haven't been mentioned yet...
> The current model for plugins is that they execute in a single-threaded
> world. Chrome maintains that model by hosting each plugin in its own process
> and RPC'ing method invocations back and forth between calling pages and the
> plugin instances. All plugin instances (of a given plugin) reside on the
> same thread.
Why can't instances of a plugin in different browser contexts be hosted in
"He was pierced for our transgressions, he was crushed for our iniquities;
the punishment that brought us peace was upon him, and by his wounds we are
healed. We all, like sheep, have gone astray, each of us has turned to his
own way; and the LORD has laid on him the iniquity of us all." [Isaiah
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the whatwg