aeronet_wt_native
A WebTransport transport implementation of aeronet, which uses the QUIC protocol under the hood to provide reliable streams and unreliable datagrams.
This transport can be used in a native app to provide a client and server transport using
wtransport as the WebTransport protocol implementation.
Using this requires the tokio async runtime.
Getting started
You must first define your app's channels - along what methods of transport can messages be sent?
Then, define your [aeronet::Message] types as described in [aeronet], and define along what
channel your message is sent.
use ;
The client and server implementations can be used separately, but have a similar API surface:
- To create a client, use [
create_client] returning a [WebTransportClient]. - To create a server, use [
create_server] returning a [WebTransportServer].
The creation process will return (WebTransport*, WebTransport*Backend) - a frontend and backend
object respectively. You should call listen on the backend in an async Tokio task as soon as
possible to start the server, then store and use the frontend within your app to interact with the
backend.
use ;
use ;