Just wondering if anyone involved in the porting effort has started poking around common/ipc_* and the channel/message objects. I started looking into what it would take to build a real render process and very quickly hit a slew of Win32 dependencies in the IPC code that need some serious untangling.
It also appears that the differences between the MessagePumps on Posix v. Win are going to spill over into these classes, and their uses upstream. One key example is IPC::Channel, a critical class in both the renderer and the browser, which subclasses MessageLoopForIO::IOHandler. IOHandler doesn't even exist for posix, so more significant thought is going to need to be applied to do the right thing for each platform. Is this already on someone's radar, or should we talk next week about a plan of attack? -- Mike Pinkerton Mac Weenie [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" 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/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
