chartered
tokio-tungstenite
Our great sponsors
chartered | tokio-tungstenite | |
---|---|---|
5 | 15 | |
129 | 1,614 | |
- | 4.2% | |
0.0 | 7.3 | |
over 1 year ago | 4 months ago | |
Rust | Rust | |
Do What The F*ck You Want To Public License | MIT License |
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.
chartered
-
Chartered (permissioned Cargo registry) now has a public instance free for all
It is currently in active development on GitHub, feel free to join in or just follow along. As it's fairly early days for a production-ready instance Chartered, you may find some surprising behaviours like being able to orphan organisations from the Web UI - "just don't do that".
-
[Media] Why do the downloads for some crates drop greatly each week? Screenshot is from the crates.io page for curl.
What strange timing for this topic to come up. Thanks for the linkback. I also published another registry a while back which is standalone, but still permissioned unlike most other registries.
-
Announcing axum 0.3
Just made the switch to 0.3 in chartered - build times are looking great compared to what they were before without boxing. Thanks for your great work
- chartered 0.1 - a private, authenticated, permissioned cargo registry for the enterprise
-
What's everyone working on this week (42/2021)?
Finishing up chartered - a private, authenticated cargo registry with fine grained per-user permissions.
tokio-tungstenite
-
How to know when can I send a message via a websocket with tokio tungstenite?
I can't help you debug your code if you do not provide it. Have you looked at the example client?
-
Yet another Web-Socket implementation in rust.
It passed all test of the autobahn testsuite And web-socket-benchmark show about 3x faster then tokio-tungstenite
-
Hey Rustaceans! Got a question? Ask here (7/2023)!
There are example files in the tokio-tungstenite crate called `autobahn-client.rs` and `autobahn-server.rs`. 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)!
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)!
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?
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
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.
-
Hey Rustaceans! Got a question? Ask here! (30/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?
tokio-tungstenite
-
help using async websocket using tokio-tungstenite
i based my code mostly on the client example from the tokio-tungstenite project: https://github.com/snapview/tokio-tungstenite/blob/master/examples/client.rs
What are some alternatives?
grenad - Tools to sort, merge, write, and read immutable key-value pairs :tomato:
async-tungstenite - Async binding for Tungstenite, the Lightweight stream-based WebSocket implementation
link-to-notion - Quick add a link to a page within Notion app
Warp - Warp is a modern, Rust-based terminal with AI built in so you and your team can build great software, faster.
CubeSimRS - Rust based Rubik's Cube simulation and solving library.
reqwest - An easy and powerful Rust HTTP Client
rescrobbled - MPRIS music scrobbler daemon
axum - Ergonomic and modular web framework built with Tokio, Tower, and Hyper
ktra - Your Little Cargo Registry
tangle - Radically simple multiplayer / networked WebAssembly
rocket_sim - An interactive rocket simulator inspired by Kerbal Space Program
warp - A super-easy, composable, web server framework for warp speeds.