How lucienlsa/cppserver works
Project type and purpose
• From the file tree (“src/Channel.cpp”, “src/Epoll.cpp”, “src/EventLoop.cpp”, “src/Server.cpp”, etc.) and the README (“30dayMakeCppServer”), we see this is a small C++ network‐server library / framework.
• It implements an event‐driven Reactor pattern on Linux (epoll under the hood), exposing classes such as Server, EventLoop, Channel, Epoll, Socket and InetAddress.
File structure
• Top‐level:
• Makefile – build script
• client03.cpp / server06.cpp – example clients/servers
• src/ – core library code
· Channel.* – wraps a single file‐descriptor + callback registration
· Epoll.* – epoll wrapping & polling
· EventLoop.* – main loop, dispatches events via Channels
· Server.* – high‐level TCP server, accepts connections, ties together EventLoop + Channels
· Socket.*, InetAddress.* – low-level socket address & helper wrappers
· util.* – small utility functions
· tmp/ – older/experimental server versions
• No thread pool is present: this is a single‐threaded Reactor.
Elements
• Client → Server.listenSocket (for TCP connect)
• Server.listenSocket → EventLoop.register(Channel)
• EventLoop → Epoll.poll() → Kernel / OS
• Kernel → ready-FDs → Epoll → EventLoop
• EventLoop → Channel.handleEvent() → Server or user callback
• Green for higher-level Server.
• Orange for low-level Socket/InetAddress.