mirror of https://github.com/fafhrd91/actix-web
This commit asserts that continuation frames are an implementation detail of the websocket layer, and should remain hidden from the application layer. That is: - a codec should write only frames to the wire, and read only frames from the wire - when sending messages, the websocket implementation should break large text and binary messages into continuation frames -- the application should not have to be aware of this. - when receiving messages, the websocket implementation should reconstitute continuation frames into their original messages -- the application should not have to handle this. - the application should only have to send and receive complete websocket messages Here, the reconstitution of continuation frames into their original messages is done by the Stream implementation of actix_web_actors::ws::WsStream, by adding a continuation frame buffer and not issuing a Poll::Ready(Some(Ok)) result until a complete message has been buffered. A test in actix_web_actors::tests::test_ws.rs checks this. The breaking of large message payloads into sequential continuation frames is done by the addition of an actix_http::ws::frame_iters module, which introduces two structs ContinuationBins and ContinuationTexts. These are iterators over either single Frame::Binary or Frame::Text frames, if the payloads are small, or over sequences of Frame::Continuation's with appropriate Items FirstBinary/FirstText, Continue, and Last. New tests in actix_http::ws::frame_iters verify this functionality. |
||
---|---|---|
.github | ||
actix-cors | ||
actix-files | ||
actix-framed | ||
actix-http | ||
actix-identity | ||
actix-multipart | ||
actix-session | ||
actix-web-actors | ||
actix-web-codegen | ||
awc | ||
benches | ||
examples | ||
src | ||
test-server | ||
tests | ||
.appveyor.yml | ||
.gitignore | ||
CHANGES.md | ||
CODE_OF_CONDUCT.md | ||
Cargo.toml | ||
LICENSE-APACHE | ||
LICENSE-MIT | ||
MIGRATION.md | ||
README.md | ||
codecov.yml | ||
rustfmt.toml |
README.md
Actix web
Actix web is a small, pragmatic, and extremely fast rust web framework
Website | Chat | Examples
Actix web is a simple, pragmatic and extremely fast web framework for Rust.
- Supported HTTP/1.x and HTTP/2.0 protocols
- Streaming and pipelining
- Keep-alive and slow requests handling
- Client/server WebSockets support
- Transparent content compression/decompression (br, gzip, deflate)
- Configurable request routing
- Multipart streams
- Static assets
- SSL support with OpenSSL or Rustls
- Middlewares (Logger, Session, CORS, etc)
- Includes an asynchronous HTTP client
- Supports Actix actor framework
Docs
Example
Dependencies:
[dependencies]
actix-web = "2"
actix-rt = "1"
Code:
use actix_web::{get, web, App, HttpServer, Responder};
#[get("/{id}/{name}/index.html")]
async fn index(info: web::Path<(u32, String)>) -> impl Responder {
format!("Hello {}! id:{}", info.1, info.0)
}
#[actix_rt::main]
async fn main() -> std::io::Result<()> {
HttpServer::new(|| App::new().service(index))
.bind("127.0.0.1:8080")?
.run()
.await
}
More examples
- Basics
- Stateful
- Multipart streams
- Simple websocket
- Tera
- Askama templates
- Diesel integration
- r2d2
- OpenSSL
- Rustls
- Tcp/Websocket chat
- Json
You may consider checking out this directory for more examples.
Benchmarks
License
This project is licensed under either of
- Apache License, Version 2.0, (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
- MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)
at your option.
Code of Conduct
Contribution to the actix-web crate is organized under the terms of the Contributor Covenant, the maintainer of actix-web, @fafhrd91, promises to intervene to uphold that code of conduct.