743005 - (e10s-device-apis) [meta] Electrolify DOM Device APIs

Status: RESOLVED FIXED

(Core :: DOM: Device Interfaces, defect)

Description

[Philipp von Weitershausen [:philikon]]

Some of the device APIs we recently added aren't multiprocess ("electrolysis") capable. With B2G aiming for to go multiprocess, we need to fix this.

Comment 1

[Philipp von Weitershausen [:philikon]]

As a general note: it's pretty painful to do e10s in C++ while we have good helpers in JS. Since most of our device APIs are backed by a JS service (RIL, IndexedDB, etc.), I suggest we use JS to communicate between chrome and content processes. The JS service in the chrome process would communicate with a corresponding object in the content process that mimics much of the same APIs for the DOM. This way should not require too many changes to the existing DOM code.

Comment 2

[Chris Jones [:cjones] inactive; ni?/f?/r? if you need me]

That's how the C++ IPC works as well.

It makes most sense for the all-JS-impl'd APIs like contacts to use JS IPC, but we need to be extremely careful about that because the JS IPC doesn't have the same sanitizing checks as the C++ layer.

Comment 3

[Chris Jones [:cjones] inactive; ni?/f?/r? if you need me]

After sms and pairing, we'll go back to just having "device APIs" and can close out this bug.