On Wed, Feb 4, 2009 at 6:07 PM, Charles Reis <cr...@chromium.org> wrote:
> This seems good-- I like the fact that the "chrome" parts of each extension
> are isolated from page content and have to use message passing. That will
> make it easier to understand which extensions actually need to access page
> content.
> One small wording question, just be sure I'm clear:
>
> "Process separation by origin is done similarly to web renderers, in that
> each extension generally gets its own process, but may share a process with
> another extension as resource constraints demand."
>
> I assume by "origin," you mean "extension?" In other words, if I have 3
> extensions installed and 10 tabs showing pages from different origins, I'll
> have 3 extension processes. (Then if I have 30 extensions installed, some
> of them will share processes.)
>
Yes. Something which was probably unclear in the doc is that each extension
will have a unique origin associated with it (something like
chrome-extension://EXTENSION_ID), so I was imagining a similar
grouping-by-origin could be done for extensions as for web content.
Thanks for the feedback.
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
