Tokio binding for Tungstenite, the Lightweight stream-based WebSocket implementation (by snapview)

Tokio-tungstenite Alternatives

Similar projects and alternatives to tokio-tungstenite

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better tokio-tungstenite alternative or higher similarity.

tokio-tungstenite reviews and mentions

Posts with mentions or reviews of tokio-tungstenite. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-02-13.
  • Hey Rustaceans! Got a question? Ask here (7/2023)!
    14 projects | | 13 Feb 2023
    There are example files in the tokio-tungstenite crate called `` and ``. Why are they called autobahn? I googled and can't understand what autobahn is all about. Is it a websocket pattern? Or some protocol?
  • Hey Rustaceans! Got a question? Ask here (5/2023)!
    19 projects | | 30 Jan 2023
    I'm using another crate that requires tls, specifically tokio-tungstenite, I'll try your suggestions later today once I get home
  • Hey Rustaceans! Got a question? Ask here (3/2023)!
    12 projects | | 16 Jan 2023
    Tokio-tungstenite - It looks like in this example, it's spamming the task thread with wakeup calls from all of the active connections. This design choice makes me doubt that this was well written in general.
  • Should i use ws-rs?
    3 projects | | 21 Aug 2022
    tokio-tungstenite is the more popular library. In frameworks, offhand Axum supports websockets (docs, example)
  • How would you refactor this code to use std's Mutex instead of Tokio's mutex
    2 projects | | 21 Aug 2022
    If you only have one task sending data to the sink, you probably don't need forward, as you can just write to the sink directly (you might not even need to split the stream in the first place, but i'm not sure about that). But often you want to write to the sink from different tasks (e.g. this example takes messages sent from one websocket connection, and broadcasts it onto every other connected websocket, so the sink for each websocket needs to be accessed by every other websocket handler task), and you can't do that with only the sink as you can't clone it. Either need to wrap it into a Mutex and clone that around the different tasks (and lock it every time you need to write to it, like OP did originally) or you can use forward to map the rx (receiver) of a channel to the sink, and clone the tx (sender) part of the channel for each task that wants to write to the sink. That way, you only have one task that is accessing the sink directly, so no issues with synchronization.
    2 projects | | 21 Aug 2022
    Yep, I assumed as much. in my example code the ws_stream is what you would get from tokio_tungstenite::accept_async. This example from the tungstenite repo shows using the forward method.
  • Hey Rustaceans! Got a question? Ask here! (30/2022)!
    12 projects | | 25 Jul 2022
    Has anyone worked with websockets before? Particularly with the tokio-tungstenite crate? I'm getting a Protocol(ResetWithoutClosingHandshake) error in my request. I send in some text, and i'm supposed to receive an audio file back.
  • What's the best production-grade websocket library in Rust?
    2 projects | | 10 Jul 2022
  • help using async websocket using tokio-tungstenite
    2 projects | | 24 May 2022
    i based my code mostly on the client example from the tokio-tungstenite project:
  • Hey Rustaceans! Got an easy question? Ask here (5/2022)!
    8 projects | | 2 Feb 2022
    I am using websocket client. How can I use proxy and set custom headers with it?
  • A note from our sponsor - InfluxDB | 24 Mar 2023
    Ingest, store, & analyze all types of time series data in a fully-managed, purpose-built database. Keep data forever with low-cost storage and superior data compression. Learn more →


Basic tokio-tungstenite repo stats
7 days ago
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives