Crates.io | sapper |
lib.rs | sapper |
version | 0.2.0 |
source | src |
created_at | 2017-09-13 06:09:50.835961 |
updated_at | 2019-10-21 08:26:46.725279 |
description | A web framework designed for easy use. |
homepage | https://github.com/daogangtang/sapper |
repository | https://github.com/daogangtang/sapper |
max_upload_size | |
id | 31557 |
size | 79,001 |
Sapper, a lightweight web framework, written in Rust.
Sapper focuses on ergonomic usage and rapid development. It can work with stable Rust.
Sapper now is based on hyper 0.10.13.
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.
In Cargo.toml,
[dependencies]
sapper = "0.1"
Now, you can boot the example server with:
cd examples/basic/
cargo build
cargo run
and open the browser, visit
http://localhost:1337/
or
http://localhost:1337/test
or any other url to test it.
more continued...
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
Typed, hierarchical control, and middlewares.
In Sapper, nearly every important thing is a Type
. They are:
Sapper's core contains only router system, request and response definitions, middleware system, and some other basic facilities. Nearly all practical features, such as query parameter, body parameter, cookie, session, json, xml, orm..., are supplied by the corresponding middlewares.
Sapper's middleware 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 middleware. Sample middleware: sapper_query.
QueryParams (x-www-form-urlencoded);
BodyParams (x-www-form-urlencoded);
BodyJsonParams;
Basic static file serving for dev;
Global object shared cross requests;
Macros;
Multipart;
sapper_query parsing query string for req;
sapper_body parsing body parameters for req, including url form encoded, json type, json to struct macro;
sapper_logger record request and caculate its time;
sapper_session a cookie plugin, and else supply a helper set_cookie function;
sapper_tmpl 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;
MIT