On Wed, Jul 15, 2009 at 16:17, Puskar Naha<[email protected]> wrote: > The IPC classes aren't involved in the WorkerPool, but I don't know what > they're for either: > http://code.google.com/p/gears/source/browse/trunk/gears/base/common/ipc_message_queue_win32.cc
If I recall correctly, that particular IPC code was for an experimental notifications Gears API that never got finished. It's not related to Chromium IPC. > One more question, where are the processor boundaries? For example, it looks > like the WorkerPool, Workers, etc are all part of a single process which is > part of Gears. The browser is a separate process. Where does the main > javascript application running inside the browser fall? The worker-related code happens in the sole Gears process. The rendering of the web page (which includes interpreting the "main" javascript) happens in the renderer process. The two processes communicate over IPC.
