mirror of
https://github.com/actix/actix-website
synced 2024-11-24 00:41:07 +01:00
2aacdf2f70
* chore: add VS Code extension recommendations * Update image URLs in README and documentation files * chore: disable no-inline-html rule * chore: use standard md/mdx syntax, and use .jsx for react components * chore: fix email links in Code of Conduct The commit message suggests fixing the email links in the Code of Conduct file to use the correct `mailto:` syntax. * chore: update actix-web error helper links Update the links to the `actix-web` error helper traits in the `databases.md` and `errors.md` files to use the correct URLs. * chore: restore unused actix-web error helper links * Update src/pages/community/coc.md Co-authored-by: Rob Ede <robjtede@icloud.com> * Update docs/getting-started.md Co-authored-by: Rob Ede <robjtede@icloud.com> --------- Co-authored-by: Rob Ede <robjtede@icloud.com>
1.5 KiB
1.5 KiB
| title |
|---|
| Connection Lifecycle |
Architecture overview
After Server has started listening to all sockets, Accept and Worker are two main loops responsible for processing incoming client connections.
Once connection accepted Application level protocol processing happens in a protocol specific Dispatcher loop spawned from Worker.
Please note, below diagrams are outlining happy-path scenarios only.
Accept loop in more detail
Most of code implementation resides in actix-server crate for struct Accept.
Worker loop in more detail
Most of code implementation resides in actix-server crate for struct Worker.
Request loop roughly
Most of code implementation for request loop resides in actix-web and actix-http crates.