commit | 8b13f96e2d4b0449e54a3665121a4302ceb56e80 | [log] [tgz] |
---|---|---|
author | Steve Anton <steveanton@webrtc.org> | Mon Nov 27 20:55:38 2017 |
committer | Commit Bot <commit-bot@chromium.org> | Mon Nov 27 20:56:00 2017 |
tree | 2622ffea2f4b2d0e103cccbc08d95758d3024575 | |
parent | f93d2800d9b0d5818a5a383def0aaef3d441df3a [diff] |
Revert "Add AddTransceiver and GetTransceivers to PeerConnection" This reverts commit f93d2800d9b0d5818a5a383def0aaef3d441df3a. Reason for revert: https://logs.chromium.org/v/?s=chromium%2Fbb%2Fchromium.webrtc.fyi%2Fios-device%2F5804%2F%2B%2Frecipes%2Fsteps%2Fcompile%2F0%2Fstdout Original change's description: > Add AddTransceiver and GetTransceivers to PeerConnection > > WebRTC 1.0 has added the transceiver API to PeerConnection. This > is the first step towards exposing this to WebRTC consumers. For > now, transceivers can be added and fetched but there is not yet > support for creating offers/answers or setting local/remote > descriptions. That support ("Unified Plan") will be added in > follow-up CLs. > > The transceiver API is currently only available if the application > opts in by specifying the kUnifiedPlan SDP semantics when creating > the PeerConnection. > > Bug: webrtc:7600 > Change-Id: I0b8ee24b489b45bb4c5f60b699bd20c61af01d8e > Reviewed-on: https://webrtc-review.googlesource.com/23880 > Commit-Queue: Steve Anton <steveanton@webrtc.org> > Reviewed-by: Peter Thatcher <pthatcher@webrtc.org> > Reviewed-by: Henrik Boström <hbos@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#20896} TBR=steveanton@webrtc.org,zhihuang@webrtc.org,hbos@webrtc.org,pthatcher@webrtc.org Change-Id: Ie91ea4988dba25c20e2532114d3a9d859a932d4c No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: webrtc:7600 Reviewed-on: https://webrtc-review.googlesource.com/26400 Reviewed-by: Steve Anton <steveanton@webrtc.org> Commit-Queue: Steve Anton <steveanton@webrtc.org> Cr-Commit-Position: refs/heads/master@{#20897}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others.
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.