Transports
dnet provides a variety of transport implementations for different networking scenarios.
Transports are implemented for both native and WebAssembly targets (when appropriate).
Provided transports
- TCP - transport over tokio’s TCP sockets (native only)
- UDP - transport over tokio’s UDP sockets (native only)
- QUIC - transports over quinn’s QUIC protocol (native only)
- WebSocket - transport over WebSockets (native and WebAssembly, both server - axum’s
WebSocketand client - tungstenite’sWebSocketon native, and web-sys’sWebSocketon WebAssembly) - MessagePort - transport over MessagePort (WebAssembly only)
- Web Worker - transport to and from a Web Worker (WebAssembly only)
- Transferable - transport for transferable objects (WebAssembly only)
- Framed transport - framed message transport
- Length-delimited transport - length-delimited message transport
- Utilities
Available for licensing
- DataChannel - transport over WebRTC data channels (native and WebAssembly)
Logging
The “logging” feature is not enabled by default. If you want transport-level diagnostics, enable it in your Cargo.toml:
[dependencies]
dnet = { version = "0.1.4", features = ["logging"] }
When the “logging” feature is enabled, supported transports implement the Logging trait. You can then enable logging at runtime and assign a logical transport name for easier filtering and debugging:
use dnet::Logging;
let mut transport = /* create transport */;
transport.set_logging_name("peer-1");
transport.enable_logging();
Named transports are especially useful when you use multiple transports of the same kind in your application.