veilid_duplex 0.1.3

Full-duplex encrypted communication between 2 nodes
docs.rs failed to build veilid_duplex-0.1.3
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Visit the last successful build: veilid_duplex-0.3.0

veilid_duplex

Full-duplex asyncronous communication between two peers with Veilid.

  • Alice publishes her route to DHT and sends DHT key to Bob. Alice will update here route on DHT when connection breaks;
  • Bob does the same, and sends his DHT key to Alice over Veilid channel.
  • When Alice or Bob fail to send a message they try getting a new route from DHT. They also update their DHT records when their routes die.
  • Sometimes a message will be delivered twice, so Alice and Bob keep a record of all hashed messages they got.

Veilid duplex manages veilid internals for you, such as allocating routes and recovering from route shutdowns.

Changlelog

  • 0.1.3 WASM support

Usage

See pingpong example.

Examples

Pingpong

2 peers increment the counter and pass it to each other.

Host:

cargo run --example pingpong -- --server --verbose

This will print host's DHT key

Client:

cargo run --example pingpong --  --verbose --client "VLD0:MDoZwLsoQgM6-XKE3giy-8r53e4yCod5Y546laT0El0"