Necko: Electrolysis design and subprojects: Difference between revisions

Necko: Electrolysis design and subprojects (view source)

335 bytes added , 27 August 2009

Confirmed users

431

edits

@@ Line 27: / Line 27: @@
 For things like HTTP redirects the current architecture shifts out the original channel and replaces it with a channel to the new destination.  This will probably require IPDL traffic to tell the content process to do something similar on its end.  There may be other occasions where IPDL traffic is needed to keep the content stubs "in sync" with what's happening in chrome necko-land.
+====miscellaneous issues====
 ;File form POSTs: bz suggested yesterday that we could accomplish this without having the content process read the file by creating a new kind of stream class, in which the content process marks the name of the file and the chrome process actually reads it from disk and uploads it.
+;Validating data:  Lucas suggested that IPDL parent actors should take measures to validate data passed to them by children, in case the latter have been compromised (ex: validating that strings are actually UTF-16). In necko's case, that should mainly be the URI and other data for the initial request.
 = Carving work into subprojects =