Confirmed users
35
edits
PeerConnection Transport Ramblings: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
<p>This page is place holder for capturing design ideas, architecture and related aspects for the RTCWeb peer-connection transport aspects. Most of the specific aspects of this discussion points to WebRTC media-engine. | <p>This page is place holder for capturing design ideas, architecture and related aspects for the RTCWeb peer-connection transport aspects. Most of the specific aspects of this discussion points to WebRTC media-engine. | ||
</p> | </p> | ||
<p>Media Flow Path | |||
Media Flow Path | </p> | ||
<pre class="_fck_mw_lspace">This section explains a typical media flow from acquisition till sending the captured media | |||
- Media Acquisition | |||
- Media Capture | |||
- Media Encoding | |||
- Media Transport | |||
On the reception side, we have the following path | </pre> | ||
<p>On the reception side, we have the following path | |||
</p> | |||
<pre class="_fck_mw_lspace"> - Media Reception | |||
- Media Decoding | |||
</pre> | |||
<p><br /> | |||
MediaEngine Resources that has to be kept in mind: | MediaEngine Resources that has to be kept in mind: | ||
- Channel | - Channel | ||
| Line 23: | Line 25: | ||
- VideoEngine Instance - one per process | - VideoEngine Instance - one per process | ||
- VoiceEngine Instance - one per process | - VoiceEngine Instance - one per process | ||
</p> | |||