4f15246683
The send queue is responsible for generating lifecycle events for all messages that are still in the queue. Because, if they are still in the queue, that means that the last fragment of the message hasn't been sent yet (because then it would have been in the retransmission queue instead). And if the last fragment hasn't been sent, the send queue is responsible for generating the `OnLifecycleMessageExpired(/*maybe_sent=*/false)` event. Bug: webrtc:5696 Change-Id: Icd5956d6aa0f392cae54f2a05bd20728d9f7f0a6 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/264144 Commit-Queue: Victor Boivie <boivie@webrtc.org> Reviewed-by: Harald Alvestrand <hta@webrtc.org> Cr-Commit-Position: refs/heads/main@{#37419}
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