WTX

Intended to group different web transport implementations.

WebSocket

Provides low and high level abstractions to dispatch frames, as such, it is up to you to implement Stream with any desired logic or use any of the built-in strategies through the selection of features.

fastwebsockets served as an initial inspiration for the skeleton of this implementation so thanks to the authors.

use wtx::{
  Stream, web_socket::{FrameBufferVec, FrameMutVec, FrameVecMut, OpCode, WebSocketClientOwned}
};

pub async fn handle_client_frames(
  fb: &mut FrameBufferVec,
  ws: &mut WebSocketClientOwned<impl Stream>
  ) -> wtx::Result<()> {
  loop {
    let frame = match ws.read_msg(fb).await {
      Err(err) => {
        println!("Error: {err}");
        ws.write_frame(&mut FrameMutVec::new_fin(fb, OpCode::Close, &[])?).await?;
        break;
      }
      Ok(elem) => elem,
    };
    match (frame.op_code(), frame.text_payload()) {
      (_, Some(elem)) => println!("{elem}"),
      (OpCode::Close, _) => break,
      _ => {}
    }
  }
  Ok(())
}

See the examples directory for more suggestions.

Performance

There are mainly 2 things that impact performance, the chosen runtime and the number of pre-allocated bytes. Specially for servers that have to create a new WebSocket instance for each handshake, pre-allocating a high number of bytes for short-lived or low-transfer connections can have a negative impact.