actix-website/content/docs/conn_lifecycle.md

---
title: Connection Lifecycle
menu: docs_architecture
weight: 1030
---

# Architecture overview

After Server has started listening to all sockets, [`Accept`][accept] and [`Worker`][worker] are two main loops responsible for processing incoming client connections.

Once connection accepted Application level protocol processing happens in a protocol specific [`Dispatcher`][dispatcher] loop spawned from [`Worker`][worker].

    Please note, below diagrams are outlining happy-path scenarios only.

![](/img/diagrams/connection_overview.svg)

## Accept loop in more detail

![](/img/diagrams/connection_accept.svg)

Most of code implementation resides in [`actix-server`][server] crate for struct [`Accept`][accept].

## Worker loop in more detail

![](/img/diagrams/connection_worker.svg)

Most of code implementation resides in [`actix-server`][server] crate for struct [`Worker`][worker].

## Request loop roughly

![](/img/diagrams/connection_request.svg)

Most of code implementation for request loop resides in [`actix-web`][web] and [`actix-http`][http] crates.

[server]: https://crates.io/crates/actix-server
[web]: https://crates.io/crates/actix-web
[http]: https://crates.io/crates/actix-http
[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
Architecture diagrams of HttpServer and Connection lifecycle (#148) * add arch diagrams and menu * fix colors for arch diagrams * refine architecture diagrams, ready for review * capitalize titles and add mmdc instruction * apply code review requested changes * Add links to accept, worker and dispatcher too 2020-01-28 12:36:35 +01:00			`---`
			`title: Connection Lifecycle`
			`menu: docs_architecture`
Fix nextup links (#153) * Fix page weights * Fix nextup link generation 2020-02-01 21:22:11 +01:00			`weight: 1030`
Architecture diagrams of HttpServer and Connection lifecycle (#148) * add arch diagrams and menu * fix colors for arch diagrams * refine architecture diagrams, ready for review * capitalize titles and add mmdc instruction * apply code review requested changes * Add links to accept, worker and dispatcher too 2020-01-28 12:36:35 +01:00			`---`

			`# Architecture overview`

fmt 2022-02-26 05:41:49 +01:00			After Server has started listening to all sockets, [`Accept`][accept] and [`Worker`][worker] are two main loops responsible for processing incoming client connections.
Architecture diagrams of HttpServer and Connection lifecycle (#148) * add arch diagrams and menu * fix colors for arch diagrams * refine architecture diagrams, ready for review * capitalize titles and add mmdc instruction * apply code review requested changes * Add links to accept, worker and dispatcher too 2020-01-28 12:36:35 +01:00
fmt 2022-02-26 05:41:49 +01:00			Once connection accepted Application level protocol processing happens in a protocol specific [`Dispatcher`][dispatcher] loop spawned from [`Worker`][worker].
Architecture diagrams of HttpServer and Connection lifecycle (#148) * add arch diagrams and menu * fix colors for arch diagrams * refine architecture diagrams, ready for review * capitalize titles and add mmdc instruction * apply code review requested changes * Add links to accept, worker and dispatcher too 2020-01-28 12:36:35 +01:00
			`Please note, below diagrams are outlining happy-path scenarios only.`

			`![](/img/diagrams/connection_overview.svg)`

			`## Accept loop in more detail`

			`![](/img/diagrams/connection_accept.svg)`

fmt 2022-02-26 05:41:49 +01:00			Most of code implementation resides in [`actix-server`][server] crate for struct [`Accept`][accept].
Architecture diagrams of HttpServer and Connection lifecycle (#148) * add arch diagrams and menu * fix colors for arch diagrams * refine architecture diagrams, ready for review * capitalize titles and add mmdc instruction * apply code review requested changes * Add links to accept, worker and dispatcher too 2020-01-28 12:36:35 +01:00
			`## Worker loop in more detail`

			`![](/img/diagrams/connection_worker.svg)`

fmt 2022-02-26 05:41:49 +01:00			Most of code implementation resides in [`actix-server`][server] crate for struct [`Worker`][worker].
Architecture diagrams of HttpServer and Connection lifecycle (#148) * add arch diagrams and menu * fix colors for arch diagrams * refine architecture diagrams, ready for review * capitalize titles and add mmdc instruction * apply code review requested changes * Add links to accept, worker and dispatcher too 2020-01-28 12:36:35 +01:00
			`## Request loop roughly`

			`![](/img/diagrams/connection_request.svg)`

Fix nextup links (#153) * Fix page weights * Fix nextup link generation 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.
Architecture diagrams of HttpServer and Connection lifecycle (#148) * add arch diagrams and menu * fix colors for arch diagrams * refine architecture diagrams, ready for review * capitalize titles and add mmdc instruction * apply code review requested changes * Add links to accept, worker and dispatcher too 2020-01-28 12:36:35 +01:00
			`[server]: https://crates.io/crates/actix-server`
			`[web]: https://crates.io/crates/actix-web`
			`[http]: https://crates.io/crates/actix-http`
fmt 2022-02-26 05:41:49 +01: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`