Media/WebRTC/WebRTCE10S: Difference between revisions
Jump to navigation
Jump to search
(Created page with "Saved") |
No edit summary |
||
Line 1: | Line 1: | ||
== 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 | |||
([[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]] |
Revision as of 15:44, 5 April 2013
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 (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