Recent changes to ThreadingConcept

ThreadingConcept modified by Sahits GmbH

Sahits GmbH — Thu, 16 Jul 2015 10:45:04 -0000

--- v3
+++ v4
@@ -1,6 +1,6 @@
 # Threads

-< Concepts 
+< [Concepts]

 This is a list of all the threads and how they are created:

ThreadingConcept modified by Sahits GmbH

Sahits GmbH — Thu, 16 Jul 2015 10:43:23 -0000

--- v2
+++ v3
@@ -1,6 +1,8 @@
 # Threads

-< [Concepts] This is a list of all the threads and how they are created: 
+< Concepts 
+
+This is a list of all the threads and how they are created: 

   * Main thread starts the Game-Clock, which is the driver for all time related events 
   * The Main thread also starts the JavaFX Application thread, the UI

ThreadingConcept modified by Sahits GmbH

Sahits GmbH — Thu, 16 Jul 2015 10:35:28 -0000

--- v1
+++ v2
@@ -5,5 +5,5 @@
   * Main thread starts the Game-Clock, which is the driver for all time related events 
   * The Main thread also starts the JavaFX Application thread, the UI 
   * The Main thread instantiates a clientServer event bus which uses a ThreadPool to propagate the events to 
-  * Basically each engine represents a separate thread. However as the whole system is event driven through the [AsyncEventBus](http://docs.guava-libraries.googlecode.com/git/javadoc/com/google/common/eventbus/AsyncEventBus.html) there is no need to define them as separate threads, which would be idling most of the time. 
+  * The actions in the engine are triggered by the [AsyncEventBus](http://docs.guava-libraries.googlecode.com/git/javadoc/com/google/common/eventbus/AsyncEventBus.html). There is no need to define separate threads for the engines, which would be idling most of the time. 
   * There are also two separate threads for the event buses which are local to the server/client

ThreadingConcept modified by Sahits GmbH

Sahits GmbH — Sat, 24 May 2014 07:22:25 -0000

Threads

< [Concepts] This is a list of all the threads and how they are created:

Main thread starts the Game-Clock, which is the driver for all time related events
The Main thread also starts the JavaFX Application thread, the UI
The Main thread instantiates a clientServer event bus which uses a ThreadPool to propagate the events to
Basically each engine represents a separate thread. However as the whole system is event driven through the AsyncEventBus there is no need to define them as separate threads, which would be idling most of the time.
There are also two separate threads for the event buses which are local to the server/client