Media/WebRTC/Architecture: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
</p><p><br /> | </p><p><br /> | ||
</p> | </p> | ||
At a high level, there are five major components we need to integrate to build a functional | |||
WebRTC stack into Firefox. | |||
* The MediaStream components that provide generic media support. | |||
* The WebRTC.org contributed code that handles RTP and codecs. | |||
* The SIPCC signaling stack. | |||
* The DataChannel management code and the libsctp code that it drives. | |||
* The transport stack (mtransport) stack which drives DTLS, ICE, etc. | |||
These are managed/integrated by the PeerConnection code which provides the PeerConnection | |||
API and maintains all the relevant state. | |||
In addition, there is the GetUserMedia() [GUM] code which handles media acquisition. However, | |||
the GUM code has no direct contact with the rest of the WebRTC stack, since the stack itself | |||
solely manipulates MediaStreams and does not care how they were created. | |||
<h2> Thread Diagram </h2> | <h2> Thread Diagram </h2> | ||
<P> | <P> | ||
=== Signaling System: CreateOffer === | === Signaling System: CreateOffer === | ||
Revision as of 01:58, 21 May 2012
Overall Architecture
At a high level, there are five major components we need to integrate to build a functional WebRTC stack into Firefox.
- The MediaStream components that provide generic media support.
- The WebRTC.org contributed code that handles RTP and codecs.
- The SIPCC signaling stack.
- The DataChannel management code and the libsctp code that it drives.
- The transport stack (mtransport) stack which drives DTLS, ICE, etc.
These are managed/integrated by the PeerConnection code which provides the PeerConnection API and maintains all the relevant state.
In addition, there is the GetUserMedia() [GUM] code which handles media acquisition. However, the GUM code has no direct contact with the rest of the WebRTC stack, since the stack itself solely manipulates MediaStreams and does not care how they were created.
Thread Diagram