Module actix_web::rt

A selection of re-exports from tokio and actix-rt.

Actix Web runs on Tokio, providing full¹ compatibility with its huge ecosystem of crates. Each of the server’s workers uses a single-threaded runtime. Read more about the architecture in actix-rt’s docs.

Running Actix Web Without Macros

use actix_web::{middleware, rt, web, App, HttpRequest, HttpServer};

async fn index(req: HttpRequest) -> &'static str {
    println!("REQ: {:?}", req);
    "Hello world!\r\n"
}

fn main() -> std::io::Result<()> {
    rt::System::new().block_on(
        HttpServer::new(|| {
            App::new().service(web::resource("/").route(web::get().to(index)))
        })
        .bind(("127.0.0.1", 8080))?
        .run()
    )
}

Running Actix Web Using #[tokio::main]

If you need to run something that uses Tokio’s work stealing functionality alongside Actix Web, you can run Actix Web under #[tokio::main]. The Server object returned from HttpServer::run can also be spawned, if preferred.

Note that actix actor support (and therefore WebSocket support through actix-web-actors) still require #[actix_web::main] since they require a System to be set up.

use actix_web::{get, middleware, rt, web, App, HttpRequest, HttpServer};

#[get("/")]
async fn index(req: HttpRequest) -> &'static str {
    println!("REQ: {:?}", req);
    "Hello world!\r\n"
}

#[tokio::main]
async fn main() -> std::io::Result<()> {
    HttpServer::new(|| {
        App::new().service(index)
    })
    .bind(("127.0.0.1", 8080))?
    .run()
    .await
}

---

1. Crates that use Tokio’s block_in_place will not work with Actix Web. Fortunately, the vast majority of Tokio-based crates do not use it. ↩

Modules

• net
  TCP/UDP/Unix bindings (mostly Tokio re-exports).
• signal
  Asynchronous signal handling (Tokio re-exports).
• task
  Task management (Tokio re-exports).
• time
  Utilities for tracking time (Tokio re-exports).

Macros

• pin
  Pins a value on the stack.

Structs

• Runtime
  A Tokio-based runtime proxy.
• System
  A manager for a per-thread distributed async runtime.
• SystemRunner
  Runner that keeps a System’s event loop alive until stop message is received.

Functions

• spawn
  Spawns a future on the current thread as a new task.