How otniel113/tugasbesarsispater works
Project type and purpose
• This is a small distributed version-control system built in Python, using a classic client-server IPC (socket) model.
• The purpose is to let a server notify clients of application updates and push new versions when available.
File structure
• Top level:
• versioning_server.py – the server process
• versioning_client.py – the client process
• README.md and a PDF report – documentation
• No subfolders or external services; the system is a two-node network (one server, one or more clients).
• Communication is direct TCP sockets; no database, no web framework.
Extract key details from the README
• System model: distributed, client-server over sockets.
• Flowcharts already defined separately for client and server internal logic.
• No third-party frameworks beyond Python’s standard library.
Capturing essential details
• Conditional branch on the server: if new version available → send payload; else → send no-update.
• Version metadata store as a persistent component.
• Optionally, annotate error handling or reconnection logic if implemented.