Do you just mean using an async context on all platforms rather than overriding a callback function in a subclass? (it's hard to tell how it used to be before it was "solved").
On Wed, Nov 26, 2008 at 7:26 PM, Darin Fisher <[EMAIL PROTECTED]> wrote: > Hopefully we can solve the callback interface issue much as it was solved > for FileStream. > -Darin > > > On Wed, Nov 26, 2008 at 10:47 AM, Mike Pinkerton <[EMAIL PROTECTED]> > wrote: >> >> 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] >> >> > > > > > -- 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 -~----------~----~----~----~------~----~------~--~---
