6e4fcac313
This reverts commit f554b3c577f69fa9ffad5c07155898c2d985ac76. Reason for revert: Parent CL breaks FYI bots. See https://webrtc-review.googlesource.com/c/src/+/206466 Original change's description: > Remove thread hops from events provided by JsepTransportController. > > Events associated with Subscribe* methods in JTC had trampolines that > would use an async invoker to fire the events on the signaling thread. > This was being done for the purposes of PeerConnection but the concept > of a signaling thread is otherwise not applicable to JTC and use of > JTC from PC is inconsistent across threads (as has been flagged in > webrtc:9987). > > This change makes all CallbackList members only accessible from the > network thread and moves the signaling thread related work over to > PeerConnection, which makes hops there more visible as well as making > that class easier to refactor for thread efficiency. > > This CL removes the AsyncInvoker from JTC (webrtc:12339) > > The signaling_thread_ variable is also removed from JTC and more thread > checks added to catch errors. > > Bug: webrtc:12427, webrtc:11988, webrtc:12339 > Change-Id: Id232aedd00dfd5403b2ba0ca147d3eca7c12c7c5 > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/206062 > Commit-Queue: Tommi <tommi@webrtc.org> > Reviewed-by: Niels Moller <nisse@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#33195} TBR=nisse@webrtc.org,tommi@webrtc.org Change-Id: I6134b71b74a9408854b79d44506d513519e9cf4d No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: webrtc:12427 Bug: webrtc:11988 Bug: webrtc:12339 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/206467 Reviewed-by: Guido Urdaneta <guidou@webrtc.org> Commit-Queue: Guido Urdaneta <guidou@webrtc.org> Cr-Commit-Position: refs/heads/master@{#33203}
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.
Development
See here for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://webrtc.googlesource.com/src
- Samples and reference apps: https://github.com/webrtc
- Mailing list: http://groups.google.com/group/discuss-webrtc
- Continuous build: http://build.chromium.org/p/client.webrtc
- Coding style guide
- Code of conduct
- Reporting bugs