1
0
Fork 0
mirror of https://github.com/actix/actix-web.git synced 2024-09-29 06:42:06 +00:00
actix-web/README.md

105 lines
4.5 KiB
Markdown
Raw Normal View History

2017-10-23 22:58:05 +00:00
# Actix web [![Build Status](https://travis-ci.org/actix/actix-web.svg?branch=master)](https://travis-ci.org/actix/actix-web) [![Build status](https://ci.appveyor.com/api/projects/status/kkdb4yce7qhm5w85/branch/master?svg=true)](https://ci.appveyor.com/project/fafhrd91/actix-web-hdy9d/branch/master) [![codecov](https://codecov.io/gh/actix/actix-web/branch/master/graph/badge.svg)](https://codecov.io/gh/actix/actix-web) [![crates.io](http://meritbadge.herokuapp.com/actix-web)](https://crates.io/crates/actix-web)
2017-09-30 16:16:59 +00:00
2017-12-05 20:25:57 +00:00
Actix web is a small, fast, down-to-earth, open source rust web framework.
```rust,ignore
use actix_web::*;
2017-12-08 20:51:44 +00:00
fn index(req: HttpRequest) -> String {
format!("Hello {}!", &req.match_info()["name"])
2017-12-05 20:25:57 +00:00
}
fn main() {
2017-12-08 20:51:44 +00:00
HttpServer::new(
2017-12-14 05:44:16 +00:00
|| Application::new()
2017-12-12 03:17:37 +00:00
.resource("/{name}", |r| r.f(index)))
2017-12-05 20:25:57 +00:00
.serve::<_, ()>("127.0.0.1:8080");
}
```
## Documentation
2017-09-30 16:16:59 +00:00
2017-11-28 03:56:14 +00:00
* [User Guide](http://actix.github.io/actix-web/guide/)
2017-10-23 22:58:05 +00:00
* [API Documentation (Development)](http://actix.github.io/actix-web/actix_web/)
* [API Documentation (Releases)](https://docs.rs/actix-web/)
2017-10-30 23:37:26 +00:00
* Cargo package: [actix-web](https://crates.io/crates/actix-web)
2017-10-07 06:14:13 +00:00
* Minimum supported Rust version: 1.20 or later
2017-09-30 16:16:59 +00:00
2017-10-07 08:12:43 +00:00
## Features
2017-12-14 07:35:21 +00:00
* Supported *HTTP/1.x* and *HTTP/2.0* protocols
* Streaming and pipelining
* Keep-alive and slow requests handling
* [WebSockets](https://actix.github.io/actix-web/actix_web/ws/index.html)
2017-11-09 03:42:13 +00:00
* Transparent content compression/decompression (br, gzip, deflate)
2017-10-23 16:17:24 +00:00
* Configurable request routing
2017-10-21 09:08:07 +00:00
* Multipart streams
2017-12-14 05:44:16 +00:00
* Middlewares (Logger, Session, DefaultHeaders)
2017-12-05 20:25:57 +00:00
* Built on top of [Actix](https://github.com/actix/actix).
2017-11-04 19:36:37 +00:00
2017-11-04 19:35:19 +00:00
## HTTP/2
Actix web automatically upgrades connection to `http/2` if possible.
### Negotiation
2017-11-09 00:48:20 +00:00
`HTTP/2` protocol over tls without prior knowlage requires
2017-11-04 19:35:55 +00:00
[tls alpn](https://tools.ietf.org/html/rfc7301). At the moment only
2017-11-04 20:49:05 +00:00
`rust-openssl` supports alpn.
```toml
[dependencies]
actix-web = { git = "https://github.com/actix/actix-web", features=["alpn"] }
```
2017-11-04 20:49:05 +00:00
Upgrade to `http/2` schema described in
2017-11-04 20:49:51 +00:00
[rfc section 3.2](https://http2.github.io/http2-spec/#rfc.section.3.2) is not supported.
2017-11-04 20:49:05 +00:00
Starting `http/2` with prior knowledge is supported for both clear text connection
2017-11-04 20:49:51 +00:00
and tls connection. [rfc section 3.4](https://http2.github.io/http2-spec/#rfc.section.3.4)
2017-11-04 20:49:05 +00:00
2017-11-09 04:25:14 +00:00
[tls example](https://github.com/actix/actix-web/tree/master/examples/tls)
2017-12-15 04:12:28 +00:00
## Benchmarks
This is totally unscientific and probably pretty useless. In real world business
logic would dominate on performance side. But in any case. i took several web frameworks
for rust and used theirs *hello world* example. All projects are compiled with
`--release` parameter. I didnt test single thread performance for iron and rocket.
As a testing tool i used `wrk` and following commands
`wrk -t20 -c100 -d10s http://127.0.0.1:8080/`
`wrk -t20 -c100 -d10s http://127.0.0.1:8080/ -s ./pipeline.lua --latency -- / 128`
I ran all tests on localhost on MacBook Pro late 2017. It has 4 cpu and 8 logical cpus.
Each result is best of five runs. All measurements are req/sec.
2017-12-15 04:29:49 +00:00
Name | 1 thread | 1 pipeline | 3 thread | 3 pipeline | 8 thread | 8 pipeline
---- | -------- | ---------- | -------- | ---------- | -------- | ----------
2017-12-15 04:48:31 +00:00
Actix | 81.400 | 710.200 | 121.000 | 1.684.000 | 106.300 | 2.206.000
Gotham | 61..000 | 178.000 | | | |
Iron | | | | | 94.500 | 78.000
Rocket | | | | | 95.500 | failed
Shio | 71.800 | 317.800 | | | | |
tokio-minihttp | 106.900 | 1.047.000 | | | |
2017-12-15 04:12:28 +00:00
Some notes on results. Iron and Rocket got tested with 8 threads,
which showed best results. Gothan and tokio-minihttp seem does not support
multithreading, or at least i couldn't figured out. I manually enabled pipelining
for *Shio* and Gotham*. While shio seems support multithreading, but it showed
absolutly same results for any how number of threads (maybe macos?)
Rocket completely failed in pipelined tests.
2017-12-05 20:25:57 +00:00
## Examples
2017-10-07 07:53:36 +00:00
2017-10-23 16:20:12 +00:00
* [Basic](https://github.com/actix/actix-web/tree/master/examples/basic.rs)
2017-10-23 18:48:06 +00:00
* [Stateful](https://github.com/actix/actix-web/tree/master/examples/state.rs)
2017-10-23 16:20:12 +00:00
* [Mulitpart streams](https://github.com/actix/actix-web/tree/master/examples/multipart)
* [Simple websocket session](https://github.com/actix/actix-web/tree/master/examples/websocket.rs)
2017-10-23 16:16:13 +00:00
* [Tcp/Websocket chat](https://github.com/actix/actix-web/tree/master/examples/websocket-chat)
2017-11-04 16:07:44 +00:00
* [SockJS Server](https://github.com/actix/actix-sockjs)
2017-10-21 09:08:07 +00:00
2017-12-05 20:25:57 +00:00
## License
2017-10-21 09:08:07 +00:00
2017-12-05 20:25:57 +00:00
Actix web is licensed under the [Apache-2.0 license](http://opensource.org/licenses/APACHE-2.0).