summaryrefslogtreecommitdiffstats
path: root/docs/controller.md
diff options
context:
space:
mode:
authorRomain Forlot <romain.forlot@iot.bzh>2018-12-14 17:55:23 +0100
committerRomain Forlot <romain.forlot@iot.bzh>2018-12-14 18:05:21 +0100
commit574c0b3a1945810774be9f649e5ca656c8dd853a (patch)
treedeb4308684bc2bc61ea7cc25f5b2d4fcbf242636 /docs/controller.md
parent0e395a67ff376a8586ac75144bd71c2944acd622 (diff)
Detail configuration key and goal of a controller
This update brings more detailled JSON object key description and try to improve what is the main goal of a controller. Change-Id: I2a4a7a3c6bf17c8e12f4bb56c8cba0d2ec048154 Signed-off-by: Romain Forlot <romain.forlot@iot.bzh>
Diffstat (limited to 'docs/controller.md')
-rw-r--r--docs/controller.md5
1 files changed, 4 insertions, 1 deletions
diff --git a/docs/controller.md b/docs/controller.md
index 4012455..bf0a3c2 100644
--- a/docs/controller.md
+++ b/docs/controller.md
@@ -8,7 +8,10 @@
## Features
* Create a controller application from a JSON config file
-* Each control (eg: navigation, multimedia, ...) is a suite of actions. When all actions succeed control is granted, if one fails control access is denied.
+* Create a controller application from a JSON config file.
+* A controller could be considered as a collection of actions that could be
+ mapped to a dynamically created verb or when receiving an event from any other
+ API.
* Actions can either be:
* Invocation of an other binding API, either internal or external (eg: a policy service, Alsa UCM, ...)
* C routines from a user provided plugin (eg: policy routine, proprietary code, ...)