Summary

• Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Parent

...	...	@@ -1,1 +1,1 @@
1		-SS14Railway.Railway Project (summer term 2014).Documentation.WebHome
	1	+Projects.Railway Project (summer term 2014).Documentation.WebHome

Author

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

Content

...	...	@@ -6,13 +6,12 @@
6	6
7	7	[[image:attach:components.png]]
8	8
9		-
10	10
11	11	== SCCharts Contoroller ==
12	12
13		-{{noformat}}
	12	+{{code}}
14	14	scccontroller.h <compiled-sccchart>.c
15		-{{/noformat}}
	14	+{{/code}}
16	16
17	17	This component is the compiled Controller-SCChart.
18	18
...	...	@@ -20,9 +20,9 @@
20	20
21	21	== Hostcode ==
22	22
23		-{{noformat}}
	22	+{{code}}
24	24	hostcode.h hostcode.c
25		-{{/noformat}}
	24	+{{/code}}
26	26
27	27	This component provides an interface to affect the railway and request events.
28	28
...	...	@@ -34,9 +34,9 @@
34	34
35	35	== Controller ==
36	36
37		-{{noformat}}
	36	+{{code}}
38	38	controller.h defaults.h controller.c
39		-{{/noformat}}
	38	+{{/code}}
40	40
41	41	The core controller component sets up a connection to the railway, maintains an environment for the synchronous tick-function and invokes the tick-function in a loop.
42	42
...	...	@@ -46,9 +46,9 @@
46	46
47	47	== State Monitor ==
48	48
49		-{{noformat}}
	48	+{{code}}
50	50	statemonitor.h statemonitor.c
51		-{{/noformat}}
	50	+{{/code}}
52	52
53	53	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.
54	54
...	...	@@ -56,13 +56,13 @@
56	56
57	57	== GUI Server ==
58	58
59		-{{noformat}}
	58	+{{code}}
60	60	guiserver.h guiserver.c
61		-{{/noformat}}
	60	+{{/code}}
62	62
63	63	The GUI server allows multiple GUI clients concurrently connecting to the controller. The number of available slots is defined in the guiserver header.
64	64
65		-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:SS14Railway.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.Railway Project (summer term 2014).Documentation.C Controller.TCP Communication.WebHome]] section.
66	66
67	67	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.
68	68