Confirmed users
147
edits
Media/WebRTC/Architecture: Difference between revisions
Added diagram illustrating internal vs external code
(Added diagram illustrating internal vs external code) |
|||
| Line 55: | Line 55: | ||
Note that each MediaPipeline is one-way, so a two-way audio flow has two media pipelines. However, since you are doing symmetric RTP, you likely have two MediaPipelines for each TransportFlow, though there may be two Transportflows for each MediaPipeline if RTCP is not muxed. | Note that each MediaPipeline is one-way, so a two-way audio flow has two media pipelines. However, since you are doing symmetric RTP, you likely have two MediaPipelines for each TransportFlow, though there may be two Transportflows for each MediaPipeline if RTCP is not muxed. | ||
==== Internal vs 3rd party code ==== | |||
<p>https://github.com/nils-ohlmeier/firefox-webrtc-documentation/raw/master/Firefox-WebRTC-internal-3rdparty.png | |||
</p><br> | |||
Colors in the diagram: | |||
* White: Mozilla's own code | |||
* Orange: 3rd party code | |||
* Green: webrtc.org code shared with Google Chrome | |||
== List of Components == | == List of Components == | ||