tungstenite-rs

Lightweight stream-based WebSocket implementation for Rust. (by snapview)

Stats

Basic tungstenite-rs repo stats
4
657
7.3
5 days ago

snapview/tungstenite-rs is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.

Tungstenite-rs Alternatives

Similar projects and alternatives to tungstenite-rs based on common topics and language

  • GitHub repo message-io

    Fast and easy-to-use event-driven network library.

  • GitHub repo criterion.rs

    Statistics-driven benchmarking library for Rust

  • GitHub repo ws-rs

    Lightweight, event-driven WebSockets for Rust.

  • GitHub repo coindesk-rs

    A Bitcoin price index API powered by coindesk.

  • GitHub repo actix-web

    Actix Web is a powerful, pragmatic, and extremely fast web framework for Rust.

  • GitHub repo async-tungstenite

    Async binding for Tungstenite, the Lightweight stream-based WebSocket implementation

  • GitHub repo yew

    Rust / Wasm framework for building client web apps

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

Posts

Posts where tungstenite-rs has been mentioned. We have used some of these posts to build our list of alternatives and similar projects - the last one was on 2021-05-08.
  • Is there a proper websockets server framework in Rust?
    reddit.com/r/rust | 2021-05-08
    https://crates.io/crates/tungstenite https://crates.io/crates/tokio-tungstenite
    reddit.com/r/rust | 2021-05-08
  • coindesk: a Free Bitcoin Price Index API Client in Rust
    reddit.com/r/rust | 2021-05-05
    If I recall rightly a lot of people use https://github.com/snapview/tungstenite-rs
  • Announcing message-io 0.12 - an event-driven message library to build network applications easy and fast. Now with zero-copy write/read messages. Performance close to using native OS socket with all the facilities the library offers.
    reddit.com/r/rust | 2021-04-08
    The usage and functionality are quite similar. The biggest API difference is that in socket-io you handle the socket itself (several listeners imply several callbacks) and with message-io you handle them at once using their endpoints as identification. But conceptually is more or less the same. Also, thanks to the great work of tungstenite-rs it has support for websockets to connect from your web client.