tower-sessions
tower
tower-sessions | tower | |
---|---|---|
1 | 14 | |
182 | 3,267 | |
- | 1.1% | |
9.3 | 2.1 | |
24 days ago | 22 days 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.
tower-sessions
-
Announcing tower-sessions 0.1.0
A few days ago I reached out for feedback regarding a potential replacement for axum-sessions in the form of tower-sessions. (Reasons for this are discussed over there.)
tower
-
Collection of trait implementations with associated types (GATs?)
This question is partially inspired by this PR which is kinda trying to do the same thing.
-
dd-trace-layer - A web application middleware for sending Datadog's trace
dd-trace-layer is a middleware for sending Datadog's trace. It's based on Tower and OpenTelemetry Rust.
-
GCP firestore and logging SDK in rust
I'm pretty sure that GCP's APIs (unlike AWS, which uses Smithy for very genuinely, very good reason) are defined using Protobuf and can be communicated with over gRPC, which means that you don't need to bind via cxx to GCP's C++ APIs. Take a look at this example using Tonic. If you're to use Tonic, you'll also be able to use Tower's middleware (main crate, http-specific) to implement retries, timeouts, tracing, and all the other things you need to be production-ready.
-
Which Rust web framework to choose in 2022 (with code examples)
#[derive(Clone)] struct MyMiddleware { inner: S, } impl Service> for MyMiddleware where S: Service, Response = Response> + Clone + Send + 'static, S::Future: Send + 'static, { type Response = S::Response; type Error = S::Error; type Future = BoxFuture<'static, Result>; fn poll_ready(&mut self, cx: &mut Context<'_>) -> Poll> { self.inner.poll_ready(cx) } fn call(&mut self, mut req: Request) -> Self::Future { println!("before"); // best practice is to clone the inner service like this // see https://github.com/tower-rs/tower/issues/547 for details let clone = self.inner.clone(); let mut inner = std::mem::replace(&mut self.inner, clone); Box::pin(async move { let res: Response = inner.call(req).await?; println!("after"); Ok(res) }) } } fn main() { let app = Router::new() .route("/", get(|| async { /* ... */ })) .layer(layer_fn(|inner| MyMiddleware { inner })); }
-
How to schedule and run cron jobs in Rust using apalis
For this tutorial, we're going to use apalis to run cron jobs in an async context. We will also look at how to decorate our jobs with tower middleware allowing us to unlock features like retries, prometheus, sentry etc
-
Warp or Rocket.rs or Actix Web?
So I have now had a look at Axum and think I will give it a try. In the readme in the repository it says something about tower or tower::Service and tonic, what exactly is that? I do not understand that yet.
-
tower-lsp 0.16.0 — Lightweight framework for building LSP servers
Better compatibility with tower ecosystem.
-
ratpack: a simpleton's HTTP framework
ratpack is idealized in the simplicity of the sinatra (ruby) framework in its goal, and attempts to be an alternative to other async HTTP frameworks such as tower, warp, axum, and tide.
-
When and how to use traits?
i would browse the standard library, tower, nom, or my own bitvec to see layout and trait/record separation. in particular, std::io and std::net may be of use: io::Read and io::Write are pervasive examples of implementing unixy file-descriptor-like behavior in the type system
-
I could use some help!
We're not there yet. I keep an eye on Tower which looks promising to build on top of. And I keep an eye on MoonZoon (full stack framework, unashamedly opinionated!).
What are some alternatives?
realworld-rust-axum-sqlx - A fullstack RealWorld implementation using rust, axum, sqlx, and yew!
hyper - An HTTP library for Rust
avored-rust-cms - Avored rust content management system
tower-lsp - Language Server Protocol implementation written in Rust
axum-login - 🪪 User identification, authentication, and authorization for Axum.
tower-http - HTTP specific Tower utilities.
rustapi - 🚀 RESTful Rust API Template / Boilerplate
bitvec - A crate for managing memory bit by bit
tower-biscuit-auth - Integrating Biscuit authentication with the Tower ecosystem.
apalis - Simple, extensible multithreaded background job and message processing library for Rust
h2 - HTTP 2.0 client & server implementation for Rust.
Tide - Fast and friendly HTTP server framework for async Rust