Crates.io | cyberdeck |
lib.rs | cyberdeck |
version | 0.1.3 |
source | src |
created_at | 2021-10-15 02:30:03.981382 |
updated_at | 2023-03-05 22:52:51.310988 |
description | A library for easily creating WebRTC data channel connections |
homepage | https://github.com/richardanaya/cyberdeck |
repository | |
max_upload_size | |
id | 465191 |
size | 96,968 |
A library for easily creating WebRTC data channel connections in Rust.
cargo add cyberdeck
let mut peer = Peer::new(|peer_id, e| async move {
match e {
PeerEvent::DataChannelMessage(c, m) => {
println!(
"{}::Recieved a message from channel {} with id {}!",
peer_id,
c.label(),
c.id()
);
let msg_str = String::from_utf8(m.data.to_vec()).unwrap();
println!(
"{}::Message from DataChannel '{}': {}",
peer_id,
c.label(),
msg_str
);
}
PeerEvent::DataChannelStateChange(c) => {
if c.ready_state() == RTCDataChannelState::Open {
println!("{}::DataChannel '{}'", peer_id, c.label());
c.send_text("Connected to client!".to_string())
.await
.unwrap();
} else if c.ready_state() == RTCDataChannelState::Closed {
println!("{}::DataChannel '{}'", peer_id, c.label());
}
}
PeerEvent::PeerConnectionStateChange(s) => {
println!("{}::Peer connection state: {} ", peer_id, s)
}
}
})
.await?;
let answer = peer.receive_offer(&offer).await?;
WebRTC works in it's most basic form by having the client and server exchange strings that represent their networking information. A signaling server is just some API that you exchange that information through. You can see a simple signaling server implemented with a single POST http handler here in this example here.
cargo run --example signaling_server
This project is licensed under either of
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted
for inclusion in cyberdeck
by you, as defined in the Apache-2.0 license, shall be
dual licensed as above, without any additional terms or conditions.