<
From version < 18.1 >
edited by Soeren Domroes
on 2025/01/30 12:05
To version < 19.1 >
edited by Soeren Domroes
on 2025/01/30 12:05
>
Change comment: Renamed back-links.

Summary

Details

Page properties
Content
... ... @@ -61,7 +61,7 @@
61 61  
62 62  The GUI server allows multiple GUI clients concurrently connecting to the controller. The number of available slots is defined in the guiserver header.
63 63  
64 -The communication is established via TCP and the message format is JSON. Each client can request the current status of the controller and interact with some commands changing most of the important properties of each train, especially the schedule. The detailed communication format and capabilities are documented in the [[doc:Projects.Railway Project (summer term 2014).Documentation.C Controller.TCP Communication.WebHome]] section.
64 +The communication is established via TCP and the message format is JSON. Each client can request the current status of the controller and interact with some commands changing most of the important properties of each train, especially the schedule. The detailed communication format and capabilities are documented in the [[doc:Projects.Archive.Railway Project (summer term 2014).Documentation.C Controller.TCP Communication.WebHome]] section.
65 65  
66 66  Most controls are performed delayed and thread-safe with the state monitor, some are directly performed via the hostcode component. Changes of the same property from different clients is processed with first-come-first-serve-principle which may cause lost update writes but will not affect the integrity of the controller.
67 67