Confirmed users
214
edits
Media/WebRTC/WebRTCE10S: Difference between revisions
Jump to navigation
Jump to search
→Network Access
| Line 49: | Line 49: | ||
All networking access in WebRTC is mediated through the ICE stack (media/mtransport/third_party/nICEr and media/mtransport/nr*). | All networking access in WebRTC is mediated through the ICE stack (media/mtransport/third_party/nICEr and media/mtransport/nr*). | ||
From a technical perspective, the requirements look like: | |||
* The ability to send and receive UDP datagrams with any valid local address and any remote address. | * The ability to send and receive UDP datagrams with any valid local address and any remote address. | ||
| Line 54: | Line 56: | ||
* The ability to have events happen at specific times. | * The ability to have events happen at specific times. | ||
Below is a schematic diagram of the interaction of the ICE stack with the rest of the system. | Below is a schematic diagram of the interaction of the ICE stack with the rest of the system which shows | ||
how things actually work. | |||
https://raw.github.com/mozilla/webrtc/master/planning/network-e10s.png | https://raw.github.com/mozilla/webrtc/master/planning/network-e10s.png | ||
As before, the boxes on the left signify the currently protected operations. | |||
There are two natural designs, discussed below. | |||
==== Network Proxies ==== | |||
==== ICE In Parent ==== | |||