Merge branch 'master' of https://github.com/eXpServer/expserver.githu…

…b.io

docs/roadmap/index.md

@@ -31,7 +31,7 @@ The eXpServer project comprises 24 stages, organized into 5 phases. Prior to the
 
 ### Phase 1: Building the core of eXpServer by creating reusable modules
 
-- 🟡 [Overview](phase-1/)
+- ✅ [Overview](phase-1/)
 - 🟡 [Stage 6: Listener & Connection Modules](phase-1/stage-6)
 - 🟡 [Stage 7: Core & Loop Modules](phase-1/stage-7)
 - 🟡 [Stage 8: Non-Blocking Sockets](phase-1/stage-8)

docs/roadmap/phase-1/stage-6.md

@@ -16,7 +16,7 @@
 - Read about the eXpServer [Architecture](/guides/resources/architecture)
 - Read the [Coding Conventions](/guides/resources/coding-conventions) for eXpServer
 
-  :::
+:::
 
 ## Introduction
 
@@ -34,6 +34,16 @@ We will utilize _netcat_ as a client for this stage to connect to eXpServer to s
 
 We will group listener and connection modules under the category _network_. Create a folder named `network` inside the `expserver/src` folder.
 
+## Design
+
+The main objective of Stage 6 is to enable eXpServer to listen on multiple ports simultaneously. This involves designing and implementing a module called `xps_listener`. Each instance of `xps_listener` module contains a socket with is bound to a specific host and port, and it is responsible for listening to incoming network connections on it.
+
+This modularization will allow eXpServer to create multiple listeners each bound to a different ports.
+
+When an `xps_listener` instance gets a client connection, an instance of `xps_connection` is created. `xps_connection` module is responsible for managing individual TCP connections between the server and clients. It encapsulates functionality related to creating, managing, and destroying individual connections.
+
+![design.png](/assets/stage-6/design.png)
+
 ## Implementation
 
 ![implementation.png](/assets/stage-6/implementation.png)
@@ -132,8 +142,6 @@ We will be constantly modifying/adding to this file in each stage to accommodate
 
 ### `main.c`
 
-<< line here >>
-
 `main.c` will contain the following:
 
 - `main()`; starting point of eXpServer. It’s main objective is to spin up listener(s) and run the event loop.

docs/roadmap/phase-1/stage-7.md

@@ -24,7 +24,7 @@ With the integration of these modules, modifications to the `xps_listener` and `
 
 ![filestructure.png](/assets/stage-7/filestructure.png)
 
-### Design
+## Design
 
 Adding to the modularization of eXpServer, in this stage, we design and implement two new modules named `xps_core` and `xps_loop`.