Wow! I did not expect this. It's fantastic to see that people are actually interested in this project, so here comes the story of Rustful:<p>It all began at the beginning 2014. I had a university project where I should build some kind of website with a database and I wanted to build it in Rust. The problem what that there was no good frameworks out there and those who existed did not compile, so I decided to roll my own. I would just need the basic routing and request handling, so it wasn't hard. I played with some words and came up with the name Rustful (combination of Rust and RESTful, but you did probably guess that) and hated it, but my friends told me that it was a great name and I thought that, well, it's silly enough to actually work. It grew on me over time.<p>Anyway, time passed and I finished my project. I thought that I could keep developing Rustful and use it for my own website and so on. I thought that I should keep it small and simple and "out of the way", because I do personally get annoyed by things that tries to control my work flow too much. There is no "The Rustful Way (tm)" to do things and it shouldn't be.<p>Time kept passing, as usual, and other frameworks started to pop up and gain followers and users. Some, like Iron, had a whole team behind them and it became hard to keep up and, at the same time, complete my studies. This eventually lead to me putting the project on ice during the summer.<p>Fast forwards to this morning. I get a mail about someone asking what the difference between Iron and Rustful is and I think "why do people still keep linking to this thing?" and then I see the torrent of stars on Github. This is when I create my HN account to write this.<p>Now I'm thinking: "Is it time to revive Rustful?"
Looks to be inspired heavily by Go's net/http package and its interfaces: <a href="http://golang.org/pkg/net/http/" rel="nofollow">http://golang.org/pkg/net/http/</a>
This is really cool -- also, I'm curious why Ogeon built this. It seems eerily similarly to what reem is trying to accomplish with IronFramework.io and what the good people at Nickel.rs are doing as well. I'd love to hear if this is trying to accomplish a fundamentally different goal or if it was more of a learning project.
With Rust's switch to 1:1 threading (soon to be not even optional AFAIK), how will this affect the concurrency capabilities of Rust-based web servers, and servers in general?
I'm curious about how these web framework crates, like this and IronFramework.io, are dealing with the imminent obsoletion of rust-http. It seems rather strange to build a completely new web framework on rust-http when it will soon be completely replaced with teepee.
This is the type of thing that will make me want to try Rust. Just glancing over the code this looks fairly clean and simple, and could be a good foundation moving forward.<p>Nice work!