WebRTCE10S: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
= Proposed WebRTC Architecture on E10S = | |||
== Introduction == | |||
The WebRTC architecture for desktop ([[Architecture]]) is based on a single process | |||
model where we can directly access platform resources from the WebRTC code. | |||
B2G, however, has a split process architecture | |||
(https://wiki.mozilla.org/B2G/Architecture) where the renderer/content process | |||
runs in a sandbox and has limited access to platform resources. Generally, | |||
it accesses them by doing IPC calls via [[IPDL|https://developer.mozilla.org/en-US/docs/IPDL]] | |||
Latest revision as of 15:31, 5 April 2013
Proposed WebRTC Architecture on E10S
Introduction
The WebRTC architecture for desktop (Architecture) is based on a single process model where we can directly access platform resources from the WebRTC code. B2G, however, has a split process architecture (https://wiki.mozilla.org/B2G/Architecture) where the renderer/content process runs in a sandbox and has limited access to platform resources. Generally, it accesses them by doing IPC calls via https://developer.mozilla.org/en-US/docs/IPDL