A rust web framework with safety and speed in mind.

I added gonzales to my literals-only benchmark (i.e. no params) and it's much slower than matchit (or my work-in-progress matcher):

test literals-full/MatchIt/20    ... bench:         608 ns/iter (+/- 17)
test literals-full/Matcher/20    ... bench:         839 ns/iter (+/- 9)
test literals-full/gonzales/20   ... bench:        2378 ns/iter (+/- 30)

test literals-full/MatchIt/200   ... bench:        9089 ns/iter (+/- 67)
test literals-full/Matcher/200   ... bench:       18144 ns/iter (+/- 289)
test literals-full/gonzales/200  ... bench:       49354 ns/iter (+/- 1211)

test literals-full/MatchIt/2000  ... bench:      210733 ns/iter (+/- 1754)
test literals-full/Matcher/2000  ... bench:      346750 ns/iter (+/- 5215)
test literals-full/gonzales/2000 ... bench:      608682 ns/iter (+/- 16586)

Each iteration makes 20/200/2000 matches against 18/180/1800 routes, full code is here.

ps. I'm mentioning this because README says that "gonzales is the fastest http router in the business" but that is not the case here.

This test fails with gonzales = "0.0.2-beta"

use gonzales::RouterBuilder;

fn main() {
    let router = RouterBuilder::new()
        .ascii_case_insensitive(false)
        .build(vec!["/Hello"]);
    let m = router.route("/Hello");
    assert!(m.is_some());
}

implements https://github.com/darpi-rs/darpi/issues/14

No need to add framework support for this. At least, not as of yet. It's sufficient to add examples.

https://github.com/darpi-rs/darpi/issues/12 https://github.com/darpi-rs/darpi/issues/10 https://github.com/darpi-rs/darpi/issues/2

Added tests and benchmarks, refactored routing, added graceful shutdown and server startup notification.

At the moment, the code generated by the app is a match statement on the parsed incoming request path. That could be improved by making additional checks on the number of slashes in a path. It could be immediately discarded, if the application doesn't have a defined route with that amount. Routes can also be grouped in different match statements based on that number and thus potentially removing some comparisons that could lead to small performance gains.

Deserialization of path variables is also doing more work than it should.

All the competition, like https://rocket.rs/ and https://actix.rs/ have nice looking websites with expansive introduction and quickstart tutorials. The big features for the framework have already been added and this is necessary for people to be able to start using the framework. It would be cool to have the first real project built with the framework to be its own representative website.

I would need help, at least for the front end. Volunteers are welcomed.

https://github.com/rust-lang/rust/issues/29661

The problem: Objects that implement the trait sometimes do not care about the container type. Therefore, it is set to std::any::Any. However, since there are no associated type defaults, there need to be 2 traits. One with a container and one without. There is an implementation of all types that implement the trait without container to implement the trait with container specifying std::any::Any. This could be simplified a lot by having the language feature mentioned above.