Rust wrappers for libdatachannel, a WebRTC Data Channels standalone implementation in C++.
This crate provides two traits that end user must implement, DataChannel and
PeerConnection, that define all available callback methods. Note that all methods have
a default no-operation implementation.
Aforementioned traits are defined as follows:
```rust pub trait DataChannel { fn onopen(&mut self) {} fn onclosed(&mut self) {} fn onerror(&mut self, err: &str) {} fn onmessage(&mut self, msg: &[u8]) {} fn onbufferedamount_low(&mut self) {} }
pub trait PeerConnection { type DC;
fn on_description(&mut self, sess_desc: SessionDescription) {}
fn on_candidate(&mut self, cand: IceCandidate) {}
fn on_conn_state_change(&mut self, state: ConnectionState) {}
fn on_gathering_state_change(&mut self, state: GatheringState) {}
fn on_data_channel(&mut self, data_channel: Box<RtcDataChannel<Self::DC>>) {}
} ```
Traits implementations are meant to be used through RtcPeerConnection and
RtcDataChannel structs.
The main struct, RtcPeerconnection, takes a Config (which defines ICE servers) and a
MakeDataChannel instance (a factory used internally for on_data_channel
callback). Note that this factory trait is already implemented for FnMut closures.
Here is the basic workflow:
```rust use datachannel::{Config, DataChannel, MakeDataChannel, PeerConnection, RtcPeerConnection};
struct Chan; impl DataChannel for Chan {}
struct Conn; impl PeerConnection for Conn {}
let iceservers = vec!["stun:stun.l.google.com:19302".tostring()]; let conf = Config::new(ice_servers);
let mut pc = RtcPeerConnection::new(&conf, Conn, || Chan)?;
let dc = pc.createdatachannel("test-dc", Chan)?; ```
Complete implementation example can be found in the tests.
By default libdatachannel will be built and linked dynamically. However there is a
static Cargo feature that will build and link it statically (with all its dependencies).
Note that CMake is required to compile libdatachannel through
datachannel-sys.