async-tungstenite
tungstenite-rs
Our great sponsors
async-tungstenite | tungstenite-rs | |
---|---|---|
1 | 15 | |
382 | 1,707 | |
- | 2.8% | |
6.9 | 7.4 | |
20 days ago | 28 days ago | |
Rust | Rust | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
async-tungstenite
-
generic purpose library in rust
You can also mix them a bit. The library tungstenite is implemented like this, and allows async-tungstenite to reuse the same logic but in a non-blocking manner. You have the API of the second option, but if a write call returns WouldBlock, you return to the caller and allow them to continue when the buffer is flushed. This can get complicated saving state though (e.g. whether it's currently doing authentication, uploading a file, etc.), but see my note below about Rust's async/await.
tungstenite-rs
-
Help with Minimal Websocket Connection
You can start by following tungstenite-rs client example. And since you are connecting to an tls enabled endpoint you should enable tls features. And according to your API's doc it requires you to send serialized json string for requesting message response and you can use serde ande serde_json for serialization. This is a complete example where a hardcode string request:
-
[I made this] – staticPi – websocket forwarder
staticpi, is a websocket forwarding service. Basically, it enables one to keep a Raspberry pi, or any computer, “connected”, in order to send and receive messages to and from any client, without having to deal with a static IP address, open ports on your router, or similar. Built in Rust, using axum, which in turn uses tungestine-rs for the websocket connections, tokio, sqlx, redis-rs and others.
-
What crate to use to make a WebSocket client
There is a client module and client examples. If using tokio, there is tokio-tungstenite on top, which has various client functions.
-
The most creative, funny, clever, ridiculous, ... library names!
tungstenite: "Lightweight stream-based WebSocket implementation. It's formerly WS2, the 2nd implementation of WS. WS2 is the chemical formula of tungsten disulfide, the tungstenite mineral."
- WebTorrent
-
What's the best production-grade websocket library in Rust?
tungstenite-rs
- Surprising Things You Didn't Know About HTTP
-
Secure Websocket Client
If you just want to connect to an existing api, async-tungstenite has a connect function. It should work with wss. See some discussion of this issue here.
- The hack that improves your tungstunite-rs performance by 160x
- Is there a proper websockets server framework in Rust?
What are some alternatives?
tokio-tungstenite - Future-based Tungstenite for Tokio. Lightweight stream-based WebSocket implementation
rust-websocket - A WebSocket (RFC6455) library written in Rust
rust-websocket-lite - A fast, low-overhead WebSocket client
ws-rs - Lightweight, event-driven WebSockets for Rust.
async-std - Async version of the Rust standard library
Rocket - A web framework for Rust.
rustpad - Efficient and minimal collaborative code editor, self-hosted, no database required
Warp - Warp is a modern, Rust-based terminal with AI built in so you and your team can build great software, faster.
another-rust-load-balancer - A load balancer with support for different middlewares and load balancing strategies, based on hyper and tokio
sockjs
delay-timer - Time-manager of delayed tasks. Like crontab, but synchronous asynchronous tasks are possible scheduling, and dynamic add/cancel/remove is supported.
warp - A super-easy, composable, web server framework for warp speeds.