One of the concerns expressed in episode #204 was that Google Chrome made UI decisions based on internal implementation. The concern was that by having a seperate process (an internal implementation detail) for each tab (a UI representation), the internal implementation was dictating design decisions.
The Chromium blog explains the multi-process architecture in more detail at http://blog.chromium.org/2008/09/multi-process-architecture.html. They create a new process for each *registered domain name*, not for each tab. If two tabs are viewing pages on the same top-level domain, they will share the same process. This is definitely not expressed correctly in the comic. The comic does explain that different sites use different processes, but also says that tabs run in different processes. The blog entry clarifies the actual implementation. Interestingly, the sandboxing based on top-level domain is a bit unfortunate (maybe), considering that Google Maps, Docs, Calendar, Groups, and Gmail are all on the same domain. Based on the blog post, there would be one process to rule them all. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
