Necko: Electrolysis design and subprojects: Difference between revisions

Necko: Electrolysis design and subprojects (view source)

507 bytes removed , 25 August 2009

Confirmed users

431

edits

@@ Line 10: / Line 10: @@
 I'm not sure if we need IPC for resource:// or view-source://.  Opinions?
-= Supporting non-e10s clients that use necko =
-We're planning to surround all IPC logic with #ifdef MOZ_IPC, and if it's not defined things should simply work for single process clients and/or clients which are otherwise allergic to e10s (apparently firefox on ppc and/or OS/2?)
-(Bsmedberg says that single-process XULRunner clients (such as Thunderbird) which aren't moving to multi-process will still work with our e10s code present: they simply won't use it.  So MOZ_IPC may just be for ppc and OS/2)
 = Implementation issues for various protocols =