49
edits
Necko: Electrolysis design and subprojects: Difference between revisions
Jump to navigation
Jump to search
Necko: Electrolysis design and subprojects (view source)
Revision as of 20:50, 5 May 2010
, 5 May 2010→Download Manager
| Line 101: | Line 101: | ||
==== Download Manager ==== | ==== Download Manager ==== | ||
The download manager should live in the chrome process. The chrome process is responsible for displaying "Where do you want to save this file?" and should be responsible for the network transfer and disk access. | |||
Issues arise in this architecture (as I understand it) because currently necko actually primarily resides in content processes. | |||
In the ideal world, necko would live in the chrome process entirely and would proxy requests for content processes. Content processes would "subscribe" to the kinds of content they're able to handle for a given request, and if no handler is subscribed, the download manager should be invoked. | |||
How should this work in the existing incarnation of necko/e10s? | |||
==== LoadGroups ==== | ==== LoadGroups ==== | ||