summaryrefslogtreecommitdiffstats
path: root/docs/part-1/1-Architecture.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/part-1/1-Architecture.md')
-rw-r--r--docs/part-1/1-Architecture.md8
1 files changed, 6 insertions, 2 deletions
diff --git a/docs/part-1/1-Architecture.md b/docs/part-1/1-Architecture.md
index 2a2417e..57a2927 100644
--- a/docs/part-1/1-Architecture.md
+++ b/docs/part-1/1-Architecture.md
@@ -22,7 +22,8 @@ Key here are on both layers, **low** and **high**.
define signaling composition with simple or complex operation to output value
from **raw** signals
-A transport plug-in is a shared library that shares a common API to be compatible with **low level** services that is:
+A transport plug-in is a shared library that shares a common API to be
+compatible with **low level** services that is:
- **open/close**: method to open a handle which could be a socket, file or
device by example.
@@ -50,7 +51,10 @@ Here is a little terminology guide to set the vocabulary:
- **action**: a function called at a certain time
- **callbacks**: a function called at a certain time
- **event**: the raw event that materialize the signal
-- **sources**: a binding API name
+- **plugins**: a C/C++ code with functions that be called by signal composer
+ service
+- **sources**: an external binding API that generate signals for the signal
+ composer service
- **signals**: an event generated by the **Application Framework**
- **virtual signals**: a signal composed of **raw signals** with value
calculated by a **callbacks**