Closed Bug 743005 (e10s-device-apis) Opened 9 years ago Closed 4 years ago
[meta] Electrolify DOM Device APIs
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.
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.
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.
Depends on: 761930
Depends on: 775997
Depends on: 791147
After sms and pairing, we'll go back to just having "device APIs" and can close out this bug.
Depends on: 791162
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.