Media/WebRTC/WebRTCE10S: Difference between revisions
Jump to navigation
Jump to search
Line 7: | Line 7: | ||
runs in a sandbox and has limited access to platform resources. Generally, | 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]] | it accesses them by doing IPC calls via [[IPDL|https://developer.mozilla.org/en-US/docs/IPDL]] | ||
The current architectural split looks like: | |||
https://raw.github.com/mozilla/webrtc/master/planning/architecture-simplified.png |
Revision as of 20:01, 6 April 2013
Introduction
The WebRTC architecture for desktop (Media/WebRTC/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
The current architectural split looks like: