How antoine-perfettini/menu-network-simulation works
This is a local C simulation of menu lookup, not a network service: a user enters a QR-style code, a client sends the identifiers through a FIFO to a router, and a data server reads the matching menu file and returns the result to that client. The router handles requests in threads while locking its shared server exchange; the server also processes requests in threads. The main workflow is visible in the excerpts. Menu files are documented by the README, but their reading was not sampled individually.
Main entry points: routeur.c Router exchange worker · client.c QR input and display · protocol.h FIFO and message protocol · serveur.c Menu lookup worker
Components 8
Client interaction
- QR input and display
src/client.c
FIFO routing
- FIFO and message protocol
include/protocol.h - Router request listener
src/routeur.c - Router exchange worker
src/routeur.c
Menu data
- Server request listener
src/serveur.c - Menu lookup worker
src/serveur.c - Menu text files
data
Other components
- Menu requester
Connections 11
- Menu requester → QR input and display: enters code
README.md - QR input and display → Router request listener: writes request
src/client.c - Router request listener → Router exchange worker: dispatches request
src/routeur.c - Router exchange worker → Server request listener: sends query
src/routeur.c - Server request listener → Menu lookup worker: dispatches query
src/serveur.c - Menu lookup worker → Menu text files: reads menu
src/serveur.c - Menu lookup worker → Router exchange worker: writes response
src/serveur.c - Router exchange worker → QR input and display: writes private response
src/routeur.c - FIFO and message protocol → QR input and display: defines messages
src/client.c - FIFO and message protocol → Router request listener: defines messages
src/routeur.c - FIFO and message protocol → Server request listener: defines messages
src/serveur.c