derliemonne/mesentask

Purpose and topology

MESEN BUTTON is a small LAN-based Python demonstration: a client exposes a one-button GUI, sends button events to a server, and the server displays a visual state change. It is intended primarily for Windows/Python 3.11.5 and normally runs across two networked machines.

Entry points

• Server process: server_viewer.py

• Client process: client_sender.py

Both programs require a matching manually configured HOST address. The server must start before the client connects.

Client interaction and event producer

client_sender.py owns the user-facing GUI. Its single button is the system’s only input surface. Pressing it triggers the client-side event path and attempts to send that event to the configured remote host.

Boundary: GUI interaction remains local; only the button action crosses the network.

Network transport boundary

The client and server communicate directly over the local network using the host values embedded in:

• client_sender.py

• server_viewer.py

There is no indicated broker, HTTP service, database, authentication layer, or persistent event store. Connectivity depends on reachable IP networking; VPN/emulated LAN software may substitute for a physical LAN.

Server receiver and visualizer

server_viewer.py is the receiving process and display owner. It opens a window initially showing an empty/black image, receives client button activity, and updates that displayed image in response.

Its responsibilities combine:

1. Binding/listening on the configured host.

2. Receiving the client signal.

3. Translating received activity into an image/window update.

Primary control flow

1. Operator configures the same server IP in server_viewer.py and client_sender.py.

2. Server starts, initializes its black display, and waits for a connection/event.

3. Client starts and connects to the server.

4. User presses the client GUI button.

5. Client transmits the button signal.

6. Server receives it and refreshes its displayed image.

Runtime and dependencies

The application runs as Python, tested with Python 3.11.5 on Windows. Python dependencies are installed from requirements.txt; the exact GUI, imaging, and networking libraries are defined there rather than in the README. No deployment infrastructure beyond two reachable hosts and Python environments is required.