13
edits
Platform/2009-05-05: Difference between revisions
Jump to navigation
Jump to search
→Multi-Process
(→Roundtable: wikilinks) |
|||
| Line 103: | Line 103: | ||
answers include: to avoid the weight of SSL/NSS in each process: to avoid complicating sharing activities for disk cache, cookies, and other shared state. we should evaluate this ourselves. | answers include: to avoid the weight of SSL/NSS in each process: to avoid complicating sharing activities for disk cache, cookies, and other shared state. we should evaluate this ourselves. | ||
bent: we probably are going to have to make significant modifications to the Chromium IPC stack, because they use RTTI/exceptions | bent: we probably are going to have to make significant modifications to the Chromium IPC stack, because they use RTTI/exceptions ([pkasting] As a Chromium contributor I can tell you authoritatively that this is untrue; we don't use or enable RTTI/exceptions anywhere in the codebase.) | ||
cjones: We should consider an IPC language, instead of a library, which we can use for typechecking and type safety, including protocol safety (e.g., read() only happens after open() and before close()). | cjones: We should consider an IPC language, instead of a library, which we can use for typechecking and type safety, including protocol safety (e.g., read() only happens after open() and before close()). | ||