2020-01-28 14:36:35 +03:00
---
title: Connection Lifecycle
---
# Architecture overview
2022-02-26 04:41:49 +00:00
After Server has started listening to all sockets, [`Accept` ][accept] and [`Worker` ][worker] are two main loops responsible for processing incoming client connections.
2020-01-28 14:36:35 +03:00
2022-02-26 04:41:49 +00:00
Once connection accepted Application level protocol processing happens in a protocol specific [`Dispatcher` ][dispatcher] loop spawned from [`Worker` ][worker].
2020-01-28 14:36:35 +03:00
Please note, below diagrams are outlining happy-path scenarios only.

## Accept loop in more detail

2022-02-26 04:41:49 +00:00
Most of code implementation resides in [`actix-server` ][server] crate for struct [`Accept` ][accept].
2020-01-28 14:36:35 +03:00
## Worker loop in more detail

2022-02-26 04:41:49 +00:00
Most of code implementation resides in [`actix-server` ][server] crate for struct [`Worker` ][worker].
2020-01-28 14:36:35 +03:00
## Request loop roughly

2020-02-01 21:22:11 +01:00
Most of code implementation for request loop resides in [`actix-web` ][web] and [`actix-http` ][http] crates.
2020-01-28 14:36:35 +03:00
[server]: https://crates.io/crates/actix-server
[web]: https://crates.io/crates/actix-web
[http]: https://crates.io/crates/actix-http
2022-02-26 04:41:49 +00:00
[accept]: https://github.com/actix/actix-net/blob/master/actix-server/src/accept.rs
[worker]: https://github.com/actix/actix-net/blob/master/actix-server/src/worker.rs
[dispatcher]: https://github.com/actix/actix-web/blob/master/actix-http/src/h1/dispatcher.rs