This document is supposed to give you a short introduction to the project.
It's purpose is to explain the project structure, so you understand where you can find the parts of code you're looking for.
This project is divided into three modules. client, daemon and shared.
client and daemon contain everything that's specific to the respective binaries of pueue and pueued. \
shared however contains everything that's used by both sides.
This includes:
- The protocol used for communicating
- Settings, since they're parsed by both binaries
- All data objects, namely
state,taskandmessage - Logging
The daemon is composed of two main components.
Both components own a Arc<Mutex<State>>, so we can guarantee a single source of truth.
It's also important to know, that there's a mpsc channel, with the TaskHandler being the consumer.
This allows notifying the TaskHandler of any special tasks that need to be done.
The daemon.socket module contains the logic for accepting client connections and receiving payloads.
The payload is then deserialized to Message and handled a the matching function.
All functions used for handling these messages can be found in daemon.instructions.
Many messages can be instantly handled by simply modifying or reading the state. \
However, sometimes the TaskHandler has to be notified, if something involves actual system processes (start/pause/kill tasks).
The TaskHandler is responsible for actually starting and handling system processes. It's further important to note, that it runs in it's own thread.
Handling tasks include:
- Starting/killing tasks
- Pausing/resuming tasks
- Handling finished tasks
- Waiting for dependencies
- Enqueueing delayed tasks
There's a lot of rather complicated code in this file.
Whenever you're editing in here, please make sure to be conservative with your state.lock() calls.
state.lock() blocks everything else!
You should always lock as late as possible and only if absolutely necessary.