Confirmed users
431
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 17:56, 27 August 2009
, 27 August 2009→miscellaneous issues
| Line 42: | Line 42: | ||
;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. | ;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. | ||
; Channel "owner": What's this frob for? Does setOwner need to propagate across chrome/content? | |||
= Carving work into subprojects = | = Carving work into subprojects = | ||