Webrtc Intro - Native APIs
来源:互联网 发布:js女装官网价位 编辑:程序博客网 时间:2024/05/21 08:57
Native APIs
The WebRTC native APIs are implemented based on the following WebRTC spec.
The code that implements WebRTC native APIs (including the Stream and the PeerConnection APIs) are availablehere. A sample client application is also provided there.
The target audience of this document are those who want to use WebRTC Native APIs to implement WebRTC JavaScript APIs or to develop native RTC applications.
The calls to the Stream APIs and the PeerConnection APIs will be proxied to the signaling thread which means that the 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 source code of the WebRTC Native API is here:
https://chromium.googlesource.com/external/webrtc/+/master/talk/app/webrtc
https://chromium.googlesource.com/external/webrtc/+/master/talk/examples
The code that implements WebRTC native APIs (including the Stream and the PeerConnection APIs) are availablehere. A sample client application is also provided there.
The target audience of this document are those who want to use WebRTC Native APIs to implement WebRTC JavaScript APIs or to develop native RTC applications.
Block diagram
Calling sequences
Set up a call
Receive a call
Close down a call
Threading model
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 2 threads or just let them be created internally.The calls to the Stream APIs and the PeerConnection APIs will be proxied to the signaling thread which means that the 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.
API documentation
- Stream APIs (mediastream.h)
- PeerConnection APIs (peerconnection.h)
Reference
The current HTML5 specification for WebRTC is here: http://dev.w3.org/2011/webrtc/editor/webrtc.htmlhttps://chromium.googlesource.com/external/webrtc/+/master/talk/app/webrtc
Client and server sample apps can be found here:
0 0
- Webrtc Intro - Native APIs
- WebRTC Native APIs
- WebRTC Native APIs[翻译]
- WebRTC Native APIs[翻译]
- WebRTC Native APIs
- WebRTC Native APIs
- WebRTC Native APIs
- Webrtc Intro - SDP
- Webrtc Intro - SDP Sample
- Webrtc Intro - SCTP
- Webrtc Intro - NetEQ
- Webrtc Intro - OpenH264 Integrate
- Webrtc Intro - kurento
- WebRTC Intro - Impact on OTT
- Intro to the three Android Audio APIs
- Intro to the three Android Audio APIs
- Webrtc Intro - RTP RTCP SDP relevants
- OpenH264 Migration into Webrtc Intro - Windows
- 【转】C++ 文件结束符
- Android Studio安装及配置心得
- JSTL function 标签 使用
- 谷歌开发工具Android Studio安装使用图文教程
- 单片机c语言
- Webrtc Intro - Native APIs
- 数字示波器的使用情况
- Android studio 安装中遇到一些问题的解决办法
- 21Hash算法以及暴雪Hash
- Redis命令学习—Hash(哈希表)操作
- Android Studio的设置教程
- 真机调试 限制设备功能
- android studio快捷键集合
- Eigen的使用