Electrolysis/Tasks

From MozillaWiki
< Electrolysis
Revision as of 16:17, 14 July 2009 by Benjamin Smedberg (talk | contribs) (IPDl/infrastructure stuff)
Jump to navigation Jump to search

This is a task list for the Electrolysis project, listing work areas, owners, mentors, etc. To volunteer for a project, please contact Benjamin Smedberg

Project Owner Mentor Bug ETA Notes
Async canvas.drawWindow for remote content Important for the Fennec UI
Implement readonly remoting of preferences (nsIPrefService/nsIPrefBranch) bsmedberg Relatively easy, good beginner project.
Remote all network access to the parent process jduell jst/biesi Need smaller subtasks!
Asynchronous and remote resolution of history queries sdwilsh bz At least the asynchronous part should land on mozilla-central
Statically check IPDL specs and C++ implementations cjones
Dynamic fuzzing/checking of cross-process infrastructure bsmedberg Fuzzing for bad data, closed sockets, crashed processes
Systematic dynamic verification of C++ code implementing IPDL protocols bsmedberg/cjones It should be possible to generate pretty exhaustive unit tests from IPDL specs...
IPDL/runtime support for shared-memory buffers Probably needed to make networking and canvas.drawWindow efficient
NPObject-over-IPC bent
Session history for remote tabs bz Need to figure out what information the parent process/UI actually use/need
Link targeting for remote tabs bz
<browser> and <tabbrowser> basically working on remote tabs bz May involve some significant rearch: data which is currently available synchronously will not be!
Refactor the Firefox context menu to work with remote tabs Events don't bubble through the content tabs the same way... will probably involve collecting necessary information on the child side and passing it to the chrome process in a trusted manner.
Implement find-in-page for remote tabs
Implement session restore for remote tabs
Crash reporting + multiple processes ted
Multi-process dashboard Shows CPU/memory usage/etc for tab and plugin processes