Necko: Electrolysis design and subprojects: Difference between revisions
Jump to navigation
Jump to search
(Created page with '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 comm…') |
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)). | ||
TODO: split work into subtasks! | TODO: split work into subtasks! | ||
<br> | |||
= protocol-specific issues = | |||
== HTTP == | |||
== HTTPS == | |||
Anything need to be done beyond work needed for HTTP? | |||
== FTP == | |||
== Other (including custom) protocols == | |||
Revision as of 21:21, 11 August 2009
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)).
TODO: split work into subtasks!
protocol-specific issues
HTTP
HTTPS
Anything need to be done beyond work needed for HTTP?