webrtc
webrtc copied to clipboard
A pure Rust implementation of WebRTC
Follows the following documents to improve APIs of webrtc-rs crates to make them more idiomatic rust: Rust API Guidelines: https://rust-lang.github.io/api-guidelines/about.html Rust Design Patterns: https://rust-unofficial.github.io/patterns/intro.html Elegant Library APIs in Rust: https://deterministic.space/elegant-apis-in-rust.html
Currently only NamedCurve::P256 is supported. https://github.com/webrtc-rs/webrtc/blob/master/dtls/src/curve/named_curve.rs
I may have missed something but I can't seem to find a way to retrieve the estimated available bandwidth when using `configure_twcc`. Is this something provided by webrtc-rs or is...
To fix a 404 not found error when running the example.
This is an initial step towards https://github.com/webrtc-rs/webrtc/issues/230. It is a brutal copy-paste from https://github.com/webrtc-rs/sctp/tree/proto over the current codebase. It doesn't compile because some of the APIs changed. My idea was...
Currently the way simulcast support is implemented(for ingress) is that each send encoding on the remote side results in a distinct track being created. i.e. ```javascript const transceiver = pc.addTransceiver(track,...
We don't support RTP retransmissions(RTX) when the retransmitted packets are sent over a separate RTP stream(with a distinct SSRC). These packets are simply black holed at the moment. For now...
## Synopsis We are currently trying to replace [Coturn](https://github.com/coturn/coturn) with this implementation. But currently it does not have alternatives to specific Coturn's functionality e.g. providing metrics, TCP fallback, external management...