commit | 264547d084d8625c60a31b15843779173d3c95b8 | [log] [tgz] |
---|---|---|
author | Per Kjellander <perkj@webrtc.org> | Mon Nov 27 08:12:01 2023 |
committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Nov 27 10:44:49 2023 |
tree | e37967dfd4259196bd83a431501abd1de00a1226 | |
parent | d0f0f38f72d92e603e909f8ef09d4f538c1aa2c7 [diff] |
Revert "Refactor AsyncTcpSocket(s) to use rtc::ReceivedPackets" This reverts commit 211daadb6658630346111c9a8ea8f67cba997952. Reason for revert: AsyncStunTCPSocket::ProcessInput , Bug introduced, not reading length of each stun message in a tcp fetch Original change's description: > Refactor AsyncTcpSocket(s) to use rtc::ReceivedPackets > > Instead of using raw pointers. > > Bug: webrtc:15368, webrtc:11943 > Change-Id: Id28a0a4fc3d00680e972bd95e0c60344c7886892 > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/328500 > Reviewed-by: Harald Alvestrand <hta@webrtc.org> > Commit-Queue: Per Kjellander <perkj@webrtc.org> > Cr-Commit-Position: refs/heads/main@{#41237} Bug: webrtc:15368, webrtc:11943 Change-Id: Id15261579a61dd200e7c3b1a013877575b87db2e Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/328760 Reviewed-by: Harald Alvestrand <hta@webrtc.org> Reviewed-by: Per Kjellander <perkj@webrtc.org> Commit-Queue: Per Kjellander <perkj@webrtc.org> Bot-Commit: rubber-stamper@appspot.gserviceaccount.com <rubber-stamper@appspot.gserviceaccount.com> Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> Cr-Commit-Position: refs/heads/main@{#41245}
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 here for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.