tokio-tungstenite
deno
Our great sponsors
tokio-tungstenite | deno | |
---|---|---|
15 | 448 | |
1,601 | 92,841 | |
3.4% | 0.4% | |
7.3 | 9.9 | |
4 months ago | about 10 hours ago | |
Rust | Rust | |
MIT 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.
tokio-tungstenite
-
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.
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)!
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
deno
-
Bun - The One Tool for All Your JavaScript/Typescript Project's Needs?
NodeJS is the dominant Javascript server runtime environment for Javascript and Typescript (sort of) projects. But over the years, we have seen several attempts to build alternative runtime environments such as Deno and Bun, today’s subject, among others.
-
Bun 1.1
https://github.com/denoland/deno/issues is the ideal place -- we try to triage all incoming issues, the more specific the repro the easier it is to address but we will take a look at everything that comes in.
-
I have created a small anti-depression script
Install Node.js (or Bun, or Deno, or whatever JS runtime you prefer) if it's not there
-
Unison Cloud
So as an end user it's kind of like https://deno.com/ where you buy into a runtime + comes prepacked with DBs (k/v stores), scheduling, and deploy stuff?
> by storing Unison code in a database, keyed by the hash of that code, we gain a perfect incremental compilation cache which is shared among all developers of a project. This is an absolutely WILD feature, but it's fantastic and hard to go back once you've experienced it. I am basically never waiting around for my code to compile - once code has been parsed and typechecked once, by anyone, it's not touched again until it's changed.
Interesting. Whats it like upgrading and managing dependencies in that code? I'd assume it gets more complex when it's not just the Union system but 3rd party plugins (stuff interacting with the OS or other libs).
-
Deno in 2023
~90MB+ at this stage and do now allow compression without erroring out. Deploying ala Golang is not feasible at that level but could well be down the line if this dev branch is picked up again!
The exe output grew from from ~50MB to plus ~90MB from 2021 to 2024: https://github.com/denoland/deno/discussions/9811 which mean Deno is worse than Node.js's pkg solution by a decent margin.
-
Mini site for recommending songs using Svelte & Deno
Behind the scenes is a simple Sveltekit-powered server function to fetch a Spotify client token then find a user's recommendation playlist and its track information. A Deno edge function to performs this data fetch and renders server-side Svelte.
-
Supercharge your app with user extensions using Deno JavaScript runtime
If your application is written in JavaScript, integrating it with JavaScript extensions is a no-brainer. However, Secutils.dev is entirely written in Rust. How would I even begin? Fortunately, I recently came across an excellent blog post series explaining how to implement your JavaScript runtime in a Rust application with Deno:
Protecting against memory-hungry scripts in Deno is more challenging. I won't go into details about how it works and instead direct you to the issue in the Deno repository with all the details. In short, you need to create a JavaScript runtime with a specific heap limit and add a callback that's invoked when the memory limits are approached. This gives you a chance to terminate the execution before Deno/V8 crashes the entire process.
- Oxlint – written in Rust – 50-100 Times Faster than ESLint
-
Deno Cron
I found the code for that here: https://github.com/denoland/deno/tree/v1.38.3/ext/cron
What are some alternatives?
ASP.NET Core - ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.
typescript-language-server - TypeScript & JavaScript Language Server
pnpm - Fast, disk space efficient package manager
esbuild - An extremely fast bundler for the web
bun - Incredibly fast JavaScript runtime, bundler, test runner, and package manager – all in one
async-tungstenite - Async binding for Tungstenite, the Lightweight stream-based WebSocket implementation
Koa - Expressive middleware for node.js using ES2017 async functions
warp-reverse-proxy - Fully composable warp filter that can be used as a reverse proxy.
zx - A tool for writing better scripts
esm.sh - A fast, smart, & global CDN for modern(es2015+) web development.
Warp - Warp is a modern, Rust-based terminal with AI built in so you and your team can build great software, faster.
nvim-lspconfig - Quickstart configs for Nvim LSP