BFPOWER/physical
2
0
Fork 0
Code Issues 2 Pull Requests Releases Activity

README.md

Browse Source
This commit is contained in:
Zachary Sunforge
2024-06-22 21:47:20 -07:00
parent 9efeaa047d
commit 9ec29910e8
1 changed files with 3 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@ -19,8 +19,6 @@ The main concepts of Physical are:
* Node: A node hosts peripherals. A node can have a commander but does not need one. A node can ignore or even override * Node: A node hosts peripherals. A node can have a commander but does not need one. A node can ignore or even override
commands from the commander. In a complex system, nodes are intended to be kept simple, less likely to commands from the commander. In a complex system, nodes are intended to be kept simple, less likely to
encounter an error than the commander, and in some cases should check for obvious problems in commands from the encounter an error than the commander, and in some cases should check for obvious problems in commands from the
commander. commander. Nodes may also communicate with one another.
* Commander: A commander hosts nodes. It is possible for a device to be both a node and a commander at the same time, * Commander: A commander hosts nodes. It performs long-running complex computation to optimize the system and gives
although it may not be the best idea to make such a setup. There is no concept of nesting commanders built into commands to nodes based on its results.
Physical. If some kind of abstraction for a computer that commands multiple commanders, which command nodes, is
necessary, it should be made for that specific application.