Confirmed users
431
edits
Necko: Electrolysis design and subprojects: Difference between revisions
Necko: Electrolysis design and subprojects (view source)
Revision as of 00:27, 14 August 2009
, 14 August 2009→protocols
No edit summary |
|||
| Line 1: | Line 1: | ||
This is a page dedicated to the design issues involved in making necko work under electrolysis (i.e. moving all network traffic to the chrome process, and using IPDL to communicate with the content process(es)). | This is a page dedicated to the design issues involved in making necko work under electrolysis (i.e. moving all network traffic to the chrome process, and using IPDL to communicate with the content process(es)). | ||
= protocols | = Which protocols need IPC? = | ||
Everyone thinks HTTP/HTTPS/FTP need to go over IPC (i.e. the content process must not be allowed to open TCP/IP connections). | |||
bz and jst give me the impression that any protocol that does file I/O should also be using IPC (so, file://, about://, jar://). But bsmedberg disagrees, and says that we'll 1) chroot the content process, so it can't cause trouble even if it's allowed to do file I/O, and 2) handle file:// requests in the chrome process. Discuss. | |||
Everyone agrees that protocols that don't do I/O don't need IPC, i.e. data://, and js:// | |||
I'm not sure if we need IPC for resource:// or view-source://. Opinions? | |||
= | = Implementation issues for various protocols = | ||
== | == HTTP == | ||
== HTTPS == | |||
Hopefully nothing special beyond the work needed for HTTP needs to be done for HTTPS to work. Fingers crossed. | |||
== FTP == | |||
== | |||
= Carving work into subprojects = | = Carving work into subprojects = | ||