By the way, if it proves to be easiest to have real named objects in the file system, we can always scope them to the browser process's user-data-dir. There is one user-data-dir per browser process, so this could allow us to solve the traditional managment issues with named objects in the filesystem. We avoid collisions, can detect stale objects on startup, etc. -Darin
On Wed, Nov 26, 2008 at 9:33 AM, Jeremy Moskovich <[EMAIL PROTECTED]>wrote: > Hi, > > I'm starting work on a pipe-based implementation of the IPC::Channel, I > just wanted to make sure no-one else was working on this in parallel. > > There are still some open questions regarding how Mach messages mesh with > libevent so until we have all the information on that, it would be good to > have something generally acceptable we can continue with. I'll post more > details once I have a complete picture. > > Paulg did some measurments on the size of IPC messages which you can find > at the end of the design document ( > http://dev.chromium.org/developers/design-documents/os-x-interprocess-communication), > turns out most of our messages are really small. > > Best regards, > Jeremy > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
