File: controllers_readme.txt

package info (click to toggle)
spring 106.0%2Bdfsg-4
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 55,316 kB
  • sloc: cpp: 543,954; ansic: 44,800; python: 12,575; java: 12,201; awk: 5,889; sh: 1,796; asm: 1,546; xml: 655; perl: 405; php: 211; objc: 194; makefile: 76; sed: 2
file content (19 lines) | stat: -rw-r--r-- 983 bytes parent folder | download | duplicates (8)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
These are the second level of control.

something high-level (workflow) can say to the controllers something like:
preferably, something highlevel:
- "attack the enemy, build what you need, request through me".
   - the higher-level will have a priority, or a percentage allocation,
     or a total allocation, for deciding which units to build as the
     requests come in

lowerlevel, not so good, these orders should be handled by lower level preferably,
  and given by a controller:
- take this group of units, "attack the enemy with these"
- take this group of units, "attack here with this"
- take this list of unit types, "attack the enemy with these, you own all the units of these types"
- take this list of unit types, say to someoen "scout the enemy with these, you own all the units of these types"

In other words, this package should be more at a "strategic" level, and
packcoordinators and so on are more at a "tactical" level, and there might
be something in between