WebRTC Native APIs
- Block Diagram
- Calling Sequences
- Threading Model
The WebRTC Native APIs implementation is based on W3C’s WebRTC 1.0: Real-time Communication Between Browsers.
Set up a call
Receive a Call
Close Down a Call
WebRTC Native APIs use two globally available threads: the signaling thread and the worker thread. Depending on how the PeerConnection factory is created, the application can either provide those two threads or just let them be created internally.
Calls to the Stream APIs and the PeerConnection APIs will be proxied to the signaling thread, which means that an application can call those APIs from whatever thread.
All callbacks will be made on the signaling thread. The application should return the callback as quickly as possible to avoid blocking the signaling thread. Resource-intensive processes should be posted to a different thread.
The worker thread is used to handle more resource-intensive processes, such as data streaming.
The current HTML5 specification for WebRTC is here:
The source code of the WebRTC Native API is here:
Client and server sample apps can be found here: