Sapper, a lightweight web framework, written in Rust.
Sapper focuses on easy of use. It can work with stable Rust (>= 1.17).
Look into json demo, you can learn how to parse http parameters, and return json;
Look into mvc diesel demo, you can learn how to use database, how to render template, and how to redirect.
[dependencies] sapper = "0.1"
Now, you can boot the example server with:
cd examples/basic/ cargo build cargo run
and open the browser, visit
or any other url to test it.
mike@mike-Vostro-3653:~/works2/wrk$ uname -a Linux mike-Vostro-3653 4.10.0-21-generic #23-Ubuntu SMP Fri Apr 28 16:14:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux mike@mike-Vostro-3653:~/works2/wrk$ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 94 model name : Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz cpu MHz : 832.183 cache size : 3072 KB bogomips : 7392.00 ... mike@mike-Vostro-3653:~/works2/sapper/examples/tiny$ cargo run --release Finished release [optimized] target(s) in 36.27 secs Running `target/release/tiny` Listening on http://127.0.0.1:1337 output: hello, world! mike@mike-Vostro-3653:~/works2/wrk$ ./wrk -t2 -c100 -d30s http://127.0.0.1:1337 Running 30s test @ http://127.0.0.1:1337 2 threads and 100 connections Thread Stats Avg Stdev Max +/- Stdev Latency 21.73us 139.92us 16.02ms 99.87% Req/Sec 235.94k 26.75k 259.73k 76.33% 7045973 requests in 30.04s, 598.04MB read Requests/sec: 234536.10 Transfer/sec: 19.91MB
- Sapper supplies only basic framework;
- Sapper only processes small request and response (with small request body, returning small response body) now;
- Three level granularity (global, module, function handler) middleware controller and unified middleware presentation;
- Typesafe abstraction, keep the same spirit with hyper;
- For easy using, will supply some convenient macros to help write business logic;
- Global object cross requests;
Sapper's philosophy is plugined, typed, hierarchical control.
Sapper's core contains only middleware/plugin system, router system, request and response definitions, and some other basic facilities. Nearly all practical features, such as query parameter, body parameter, cookie, session, json, xml, orm..., are supplied by the outer plugins.
Sapper's plugin is very easy to write. One rust module realized a function on the prototype of
fn (&mut Request) -> Result<()>; // before plugin fn (&Request, &mut Response) -> Result<()>; // after plugin
can be thought as Sapper's plugin. Sample template please refer sapper_query plugin.
In Sapper, nearly every important thing is a
Type. They are:
- Each module is a type, different modules are different types;
- Every plugin supply 0~n types for handler getting values;
- Inherited from hyper's typed spirit, all headers, mime and so on should use types for manipulation.
- Sapper forces you to put router in each module (in main.rs, you can not write it, no space left for you to write);
- Sapper forces you to seperate the router binding and the handler realization;
- Sapper's plugin processor can be used in app level wrapper, module level wrapper, and each handler. These three level hierarchical controls make it flexible to construct your business.
- QueryParams (x-www-form-urlencoded);
- BodyParams (x-www-form-urlencoded);
- Basic static file serving for dev;
- Global object shared cross requests;
- QueryParams parsing query string for req;
- BodyParams parsing body parameters for req, including url form encoded, json type, json to struct macro;
- Logger record request and caculate its time;
- SapperSession a cookie plugin, and else supply a helper set_cookie function;
- Template use tera to render template;
Thanks to these projects below:
- hyper Sapper is based on hyper mio branch;
- iron Sapper learns many designs from iron;
- router Sapper steals router about code from it;
- recognizer Sapper uses this route recognizer;