Thanks Adam! Before we start creating a list, we should think of a procedure that will make sure it is kept up-to-date. It makes no sense if we create the list now only to find that a year from now, when we need it, it's outdated.
The two most important questions to me at this point are: - Were should we keep this information? - How do we keep this information up-to-date when code changes? Thanks, BJ Berend-Jan Wever (skyli...@google.com) | Security Software Engineer Google Netherlands B.V. | Reg: Claude Debussylaan 34, 15th floor 1082 MD Amsterdam 34198589 | NETHERLANDS | VAT / Tax ID:- 812788515 B01 On Sun, Jun 14, 2009 at 19:22, Adam Langley <a...@chromium.org> wrote: > On Thu, Jun 11, 2009 at 8:59 AM, Berend-Jan Wever<skyli...@chromium.org> > wrote: > > All in all this means that it would be very useful to maintain a list > > of implementation and design differences between the various ports. I > > am looking for practical and efficient ways to create and maintain > > such a list. Ideally, it should be easy/mandatory to update the list > > to prevent it from ever becoming out-dated. > > I can start do a brain dump of the current differences between the > Linux and Windows port: > We have a secondary IPC system: > http://code.google.com/p/chromium/wiki/LinuxSandboxIPC > We have a different process model: > http://code.google.com/p/chromium/wiki/LinuxZygote > We will soon be using harfbuzz in the renderer to perform complex > text shaping. > > That's all the security sensitive stuff which pops into mind. > > Cheers > > AGL > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
