54e4e35c89
The buffer of reassembled messages in ReassemblyQueue is only to be used while processing a DATA/I-DATA or FORWARD-TSN as processing these chunks may result in assembling messages. When the socket is idle - between API calls - it's supposed to be empty. Instead of having it as a member in ReassemblyQueue, it could be provided as an argument to ReassemblyQueue::Add and ReassemblyQueue::Handle(ForwardTSN), but that would be a quite big refactoring. That will be investigated separately. Bug: None Change-Id: I41238de28f32f2a622c1d045debe3ea11e7c23f6 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/232000 Reviewed-by: Florent Castelli <orphis@webrtc.org> Commit-Queue: Victor Boivie <boivie@webrtc.org> Cr-Commit-Position: refs/heads/main@{#35014}
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: https://ci.chromium.org/p/webrtc/g/ci/console
- Coding style guide
- Code of conduct
- Reporting bugs
- Documentation