Summary

• Page properties (3 modified, 0 added, 0 removed)
• Attachments (0 modified, 1 added, 0 removed)
  • components.png
• Objects (1 modified, 0 added, 0 removed)
  • Confluence.Code.ConfluencePageClass[0]

Details

Page properties

Parent

...	...	@@ -1,0 +1,1 @@
	1	+Documentation

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.als
	1	+XWiki.csp

Content

...	...	@@ -52,7 +52,7 @@
52	52	statemonitor.h statemonitor.c
53	53	{{/noformat}}
54	54
55		-The state monitor component allows a thread-safe communication between connected GUIs and the running controller. This communication is also tick-safe meaning that changes are only applied at tick-borders. In addition to that the communication is mutual exculded without blocking the controller thread and thus the controller remains a reactive system.
	55	+The state monitor component allows a thread-safe communication between connected GUIs and the running controller. This communication is also tick-safe meaning that changes are only applied at tick-borders. In addition to that the communication is mutual excluded without blocking the controller thread and thus the controller remains a reactive system.
56	56
57	57	Furthermore it allows the generation of the current state of the controller in JSON format.
58	58
...	...	@@ -62,11 +62,11 @@
62	62	guiserver.h guiserver.c
63	63	{{/noformat}}
64	64
65		-The GUI server allows multiple GUI cilent a concurrently connection to the controller. The number of available slots is defined in the guiserver header.
	65	+The GUI server allows multiple GUI clients concurrently connecting to the controller. The number of available slots is defined in the guiserver header.
66	66
67	67	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:TCP Communication]] section.
68	68
69		-All 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 process with first-come-first-serve-principle which may cause lost update writes but will not affect the integrity of the controller.
	69	+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.
70	70
71	71	= Interaction =
72	72

components.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.XWikiGuest

Size

...	...	@@ -1,0 +1,1 @@
	1	+124.5 KB

Content

Confluence.Code.ConfluencePageClass[0]

Id

...	...	@@ -1,1 +1,1 @@
1		-9471742
	1	+9471698

URL

...	...	@@ -1,1 +1,1 @@
1		-https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/SS14Railway/pages/9471742/C Controller
	1	+https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/SS14Railway/pages/9471698/C Controller