futures-rs
actix-web
futures-rs | actix-web | |
---|---|---|
11 | 171 | |
5,235 | 20,249 | |
0.6% | 1.0% | |
8.4 | 9.1 | |
about 1 month ago | 7 days ago | |
Rust | Rust | |
Apache License 2.0 | 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.
futures-rs
-
Which async channel is best?
So this is actually better than true fairness (true fairness would lead to deadlock if a sender is forgotten). It is a pity that the there does not seem to be resources that document this design. There is this old thread where Carl provides some background, but I found it personally a bit hard to follow.
-
Async cancellation: a case study of pub-sub in mini-redis
Is this still true after it switched to using FuturesOrdered?
-
I don't really understand how I'm supposed to use async
Done.
-
Confused about how to use tokio to process a vector in parallel
You can use Streams, which are the async version of Iterators; They aren't stable yet, so you'll have to use a crate such as futures.
-
What crates would you consider essential?
futures
-
How to architect Rust code on Async/Await
For traits, like AsyncRead and AsyncWrite, go with the futures crate.
-
Async Rust in Practice: Performance, Pitfalls, Profiling
Here is the PR: https://github.com/rust-lang/futures-rs/pull/2551
Yield = wake the `waker_ref`. Avoiding the yield would be clone().wake().
That said, "poll immediately" isn't actually a thing nor was it ever a thing except in incorrect implementations.
-
What sort of mature, open-source libraries do you feel Rust should have but currently lacks?
Rust lacks an implementation of ReactiveX. futures/futures-signals seems to be the the ecosystem equivalent but I'm sure there'd be a lot of interest in an actual implementation.
-
Why isn't `rc::Weak<T>` marked `UnwindSafe`when T is `RefUnwindSafe`?
The opposite problem exists as well. Many types are actually unwind safe, but do not get the autotrait. In that case authors would have to manually declare them UnwindSafe. Because this is rarely done, having an API with a trait bound T: UnwindSafe is rarely viable in terms of ergonomics. It now obliges client code to wrap all calls to your API in AssertUnwindSafe which, if they use types from third party libraries, obliges them to assert this is fine. example
-
futures 0.3.9 released with big improvement in compile time
Also, we plan to give users more control in the future. See https://github.com/rust-lang/futures-rs/issues/2207, https://github.com/rust-lang/futures-rs/issues/2295, etc. for this
actix-web
-
Empowering Web Privacy with Rust: Building a Decentralized Identity Management System
Actix Web Documentation: Detailed documentation on using Actix-web, including examples and best practices for building web applications with Rust.
-
Ntex: Powerful, pragmatic, fast framework for composable networking services
I can't speak to the "is it any good" part, but (after a bit of research) I can share what I've found. I'll try to represent things as best as I understand, but I may have some finer details mixed up.
ntex is written by the same person that started actix-web, Nikolay Kim (fafhrd91 on GitHub). There was a bunch of drama a while back due to actix-web using (what many reasoned to be) avoidable unsafe code, which was later found to be buggy. Nikolay was pilloried online, resulting in him transferring leadership of actix-web to someone else. ntex is, as I understand it, essentially Nikolay picking back up on his ideals for what could have been actix-web, if people hadn't pushed him out of his own project.
How ntex compares to the pre-/post-leadership change of actix-web, I don't know.
Here are some jumping points if you want more of the backstory.
https://www.theregister.com/2020/01/21/rust_actix_web_framew...
https://steveklabnik.com/writing/a-sad-day-for-rust
https://github.com/actix/actix-web/issues/1289
-
Building a REST API for Math Operations (+, *, /) with Rust, Actix, and Rhai🦀
Are you ready to embark on another journey in Rust? Today, we'll explore how to create a REST API that performs basic mathematical operations: addition, multiplication, and division. We'll use Actix, a powerful web framework for Rust, together with Rhai, a lightweight scripting language, to achieve our goal.
- Actix-Web: v4.5.0
-
Getting Started with Actix Web - The Battle-tested Rust Framework
Within actix-web, middleware is used as a medium for being able to add general functionality to a (set of) route(s) by taking the request before the handler function runs, carrying out some operations, running the actual handler function itself and then the middleware does additional processing (if required). By default, actix-web has several default middlewares that we can use, including logging, path normalisation, access external services and modifying application state (through the ServiceRequest type).
- Show HN: Play Euchre with AI Bots
- Actix-Web: v4.4.0
- Choosing the Right Rust Web Framework: An Overview
-
Building a Rust app with Perseus
Rust is a popular system programming language, known for its robust memory safety features and exceptional performance. While Rust was originally a system programming language, its application has evolved. Now you can see Rust in different app platforms, mobile apps, and of course, in web apps — both in the frontend and backend, with frameworks like Rocket, Axum, and Actix making it even easier to build web applications with Rust.
-
Introducing SQLPage : write websites entirely in SQL
actix to handle HTTP requests
What are some alternatives?
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
axum - Ergonomic and modular web framework built with Tokio, Tower, and Hyper
async-std - Async version of the Rust standard library
Rocket - A web framework for Rust.
carboxyl - Functional Reactive Programming library for Rust
Tide - Fast and friendly HTTP server framework for async Rust
mioco - [no longer maintained] Scalable, coroutine-based, fibers/green-threads for Rust. (aka MIO COroutines).
tonic - A native gRPC client & server implementation with async/await support.
tangle - Deprecated - Use https://github.com/alexcrichton/futures-rs instead
hyper - An HTTP library for Rust
coio-rs - Coroutine I/O for Rust
salvo - A powerful web framework built with a simplified design.