Confirmed users
214
edits
Media/WebRTC/Architecture: Difference between revisions
Jump to navigation
Jump to search
→List of Components
No edit summary |
|||
| Line 58: | Line 58: | ||
The system has the following main components, in no particular order | The system has the following main components, in no particular order | ||
* PeerConnection | |||
** PeerConnection.js -- shim translation layer to let us do API adaptation to the C++ | |||
** PeerConnectionImpl -- C++ implementation of the PeerConnection interface. | |||
** SIPCC -- handles SDP and media negotiation. Provided by Cisco but not a downstream. | |||
* Media | * Media | ||
** Webrtc.org/GIPS -- handles media encoding and decoding. Downstream from Google. | ** Webrtc.org/GIPS -- handles media encoding and decoding. Downstream from Google. | ||
** MediaConduit -- Generic wrapper around Webrtc.org | ** MediaConduit -- Generic wrapper around Webrtc.org | ||
** MediaPipeline -- Wrapper to hold the MediaConduit, mtransport subsystem, and the SRTP contexts, as well as interface with MediaStreams. | |||
* Transport | |||
** mtransport -- generic transport subsystem with implementations for ICE, DTLS, etc. | |||
** NSS -- new DTLS stack. Mentioned because we need to land the new version of NSS | |||
** nICEr -- ICE stack; downstream from reSIProcate project | |||
** nrappkit --portable runtime, utility library; downstream from nrappkit.sourceforge.net | |||
* | * DataChannel | ||
** DataChannel implementation in the DOM | |||
** libsctp -- SCTP implementation; downstream from the BSD SCTP guys | |||