Combining "SetTransportChannel" and "SetRtcpTransportChannel".

The only real difference between the two is that SetRtcpTransportChannel
had a workaround to prevent a signal from being emitted early.
Basically, in SetTransport, we want to switch the transport channels and
*then* update the state, rather than updating the state after changing
only one transport channel.

But this can be accomplished more easily by simply updating the state in
SetTransport directly.

Review-Url: https://codereview.webrtc.org/2274283004
Cr-Commit-Position: refs/heads/master@{#13945}
2 files changed
tree: 7975560cbadb1eb38d4c4b482c71047173861a64
  1. .clang-format
  2. .gitignore
  3. .gn
  4. AUTHORS
  5. BUILD.gn
  6. COPYING
  7. DEPS
  8. LICENSE
  9. LICENSE_THIRD_PARTY
  10. OWNERS
  11. PATENTS
  12. PRESUBMIT.py
  13. README.md
  14. WATCHLISTS
  15. all.gyp
  16. build_overrides/
  17. check_root_dir.py
  18. chromium/
  19. codereview.settings
  20. data/
  21. infra/
  22. license_template.txt
  23. pylintrc
  24. resources/
  25. setup_links.py
  26. sync_chromium.py
  27. talk/
  28. third_party/
  29. tools/
  30. webrtc/
README.md

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. This page is maintained by the Google Chrome team.

Development

See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.

More info