How osasazamegbe/http-server works
This educational C++ HTTP server accepts TCP connections synchronously and returns a fixed HTML response. The README describes a listening socket, queued connections, request reading, and a dummy response; the excerpts show the concrete accept/read/respond loop, but no thread queue or request parsing. Linux and Windows implementations are separate. The edges below follow the shown entry points and calls; the Linux executable’s build/runtime wiring is documented but not shown in an excerpted build configuration.
Main entry points: http_tcpserver.cpp Windows TCP server · http_tcpServer_linux.cpp Linux TCP server · server.cpp Windows entry · server_linux.cpp Linux entry
Components 7
Executables
- Windows entry
server.cpp - Linux entry
server_linux.cpp
Windows server
- Windows TCP server
http_tcpserver.cpp - Windows server interface
http_tcpserver.h
Linux server
- Linux TCP server
http_tcpServer_linux.cpp - Linux server interface
http_tcpServer_linux.h
Other components
- HTTP client
Connections 8
- Windows entry → Windows TCP server: starts listening
server.cpp - Linux entry → Linux TCP server: starts listening
server_linux.cpp - HTTP client → Windows TCP server: connects to
README.md - HTTP client → Linux TCP server: connects to
README.md - Windows TCP server → HTTP client: sends response
http_tcpserver.cpp - Linux TCP server → HTTP client: sends response
http_tcpServer_linux.cpp - Windows TCP server → Windows server interface: implements
http_tcpserver.h - Linux TCP server → Linux server interface: implements
http_tcpServer_linux.h