Necko: Electrolysis design and subprojects: Difference between revisions

Jump to navigation Jump to search
Line 13: Line 13:
= Supporting single-process (and possibly standalone) necko? =
= Supporting single-process (and possibly standalone) necko? =


== Supporting single-process necko ==
== Supporting non-e10s clients that use necko ==


We should be able to support single-process XULRunner clients (such as Thunderbird) which aren't moving to multi-process.  I'm planning to surround all IPC logic with #ifdef MOZ_IPC, and if it's not defined things should simply work for single process.  
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)


== Worth continuing "Standalone" necko? ==
== Worth continuing "Standalone" necko? ==
Confirmed users
431

edits

Navigation menu