Rusty Rain

I don’t have too much preference, just want to simplify the dependency on one crypto crate.

sctp-proto is actively developing in branch https://github.com/webrtc-rs/sctp/tree/proto.

cargo build --release --example data-channels-flow-control increases performance, but not comparable to pion. ./target/release/examples/data-channels-flow-control Press ctlr-c to stop Peer Connection State has changed: connected (offerer) Peer Connection State has changed: connected...

thanks @vitdevelop and @whans for the benchmarking. Look like we need some efforts to profile the hotspots/bottlenecks.

@vitdevelop, thanks for the finding. Could you submit a PR to add tokio-console/console_subscriber to data-channels-flow-control example? so, I can take a look.

Move to https://github.com/webrtc-rs/turn/issues/1

For example, don't use std::sync::Mutex or parking_lot::Mutex on the following case, which hold the lock across the .await point. ``` async fn work(mtx: &Mutex) { println!("lock"); { let mut v...

it is ok to use std::sync::Mutex or parking_lot::Mutex when it is not across the .await point, for example: ``` async fn work(mtx: &Mutex) { println!("lock"); { let mut v =...

I created the SFU repo : https://github.com/webrtc-rs/sfu you can work on this dedicated SFU repo

sounds great!