The FastCGI Rust implementation.
Iron
The FastCGI Rust implementation. | Iron | |
---|---|---|
- | 8 | |
8 | 6,122 | |
- | 0.0% | |
0.0 | 0.0 | |
over 1 year ago | over 1 year 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.
The FastCGI Rust implementation.
We haven't tracked posts mentioning The FastCGI Rust implementation. yet.
Tracking mentions began in Dec 2020.
Iron
-
Options for thread-per-request or thread-per-connection web servers?
I've written many things using Iron and it's been fine. It's not particularly developed any more but I am not aware of any major outstanding issues.
-
Rocket v0.5-rc3 is out!
I don't miss the time when we basically only had Iron
-
Which Rust web framework to choose in 2022 (with code examples)
iron
-
How do I chiose rust web framework in 2022?
There're many web framework in rust, such as SergioBenitez/Rocket , actix/actix-web ,poem-web/poem , iron/iron . How do I chiose, anyone suggestion?
-
Noob Help
I'm not sure which definition of backend you are thinking of here. In case you simply mean "server side", here are a couple of libraries that might be of use: iron - been a while since I used it, used it for a couple smaller projects rocket (nightly only) - no personal experience, but a lot of people seem to like it diesel - a bit complex to wrap your head around, but once you get the idea it's really nice. Definitely check out the examples.
-
Whats your favourite open source Rust project that needs more recognition?
it's taken by a web framework https://github.com/iron/iron
-
Building a shared vision for Async Rust
Your comment touches on a few misconceptions I see a lot.
Firstly, `reqwest` exposes both an async and a synchronous API, allowing the developer to choose which one to use. They are largely interchangeable code-wise. [1]
Secondarily, and more broadly, async is possible to opt out of. You must understand that most web and network related libraries will be async by default for performance, because people who write in Rust and people who write web servers typically care greatly about performance. This is the intersection of those two groups. That being said, there are options outside of that ecosystem. [2]
If you truly want to use an asynchronous library without migrating your application to run entirely on an async runtime like tokio, you can run it inside of a synchronous function without much trouble. I've put together a playground link for you. [3]
1. https://docs.rs/reqwest/0.11.2/reqwest/blocking/index.html
2. Iron: https://github.com/iron/iron
-
Porting a serverless chatbot from Python to Rust
There are several web frameworks for Rust: Rocket, Actix, Warp, Iron - but only Actix has released a stable 1.0 release, and there has been considerable controversy over how it uses unsafe Rust.
What are some alternatives?
actix-web - Actix Web is a powerful, pragmatic, and extremely fast web framework for Rust.
Rocket - A web framework for Rust.
Tide - Fast and friendly HTTP server framework for async Rust
Gotham - A flexible web framework that promotes stability, safety, security and speed.
Sapper - A lightweight web framework built on hyper, implemented in Rust language.
rust-musl-builder - Docker images for compiling static Rust binaries using musl-libc and musl-gcc, with static versions of useful C libraries. Supports openssl and diesel crates.
frank_jwt - JSON Web Token implementation in Rust.
tiny-http - Low level HTTP server library in Rust
kanidm - Kanidm: A simple, secure and fast identity management platform