Crate aeronet_webtransport 

aeronet_io implementation using WebTransport for data transfer over QUIC, compatible with both native and WASM.

This uses xwt-wtransport via wtransport on native, and xwt-web on WASM. The server implementation is only available on native targets.

Feature flags

• client — Enables the client module.

• dangerous-configuration — Enables wtransport/dangerous-configuration, allowing you to use potentially dangerous certificate validation configurations.

  You should not use dangerous configurations in production builds of your app.

• document-features — Enable this when generating docs.

• self-signed (enabled by default) — Enables wtransport/self-signed, allowing you to generate self-signed certificates easily for use in a server.

  Note that, without explicitly allowing your server’s self-signed certificate (or using dangerous-configuration and disabling certificate validation), clients will not be able to connect to a server with self-signed certificates.

• server — Enables the server module.

Re-exports

pub use wtransport;

Modules

cert

Utilities for working with X.509 certificates.

clientclient

See WebTransportClient.

serverserver

See WebTransportServer.

session

Implementation for WebTransport sessions, shared between clients and servers.

Structs

WebTransportRuntime

Provides a platform-agnostic way to spawn futures for driving the WebTransport IO layer.