Mastersystem Remake #28
Description
Currently one or more plugins have to designate themselves as "master." Otherwise the plugin will not POST / PATCH updates and the backend will have no current data. Currently this has to be done by the controller manually. Multiple masters at the same airport are possible, but this is unintended. Side-effects have not been discovered yet.
Therefor goal is to replace this system. The idea so far:
The backend utilizes the VATSIM datafeed. This avoids being dependable on controllers being online for data and allows to compute times beforehand.
If a controller is online the backend can utilize the data provided by their plugin. We will have to determine if that is actually required, in theory the updates from the plugin should be more frequent.
The plugin will have three modes.
Master: The plugin sends data updates (primarily position, flightplan etc.) to the backend. Requires controller to be connected. Unlike in V1, this mode cannot be set manually. It is determined by the backend.
Controlling: TagFunctions to set times are forwarded. Requires controller to be connected. Possible default mode after connecting.
Observing: Data is only being received, tag functions are disabled / don't send times. Default for observers, can also be selected manually.
However Sweatbox sessions should also work with the plugin as we need the possibilty to test the plugin and it would allow operators to test the whole system and especially their taxizones / -times.