+
Overview of AFB-DAEMON
======================
- version: 1
- Date: 30 mai 2016
- Author: José Bollo
-
-
Roles of afb-daemon
-------------------
On the following figure, you can use a typical use
of afb-daemon:
-<a id="binder-fig-basis"><h4>Figure: binder afb-daemon, basis</h4></a>
-
- . . . . . . . . . . . . . . . . . . . . . . . . . .
- . Isolated security context .
- . .
- . +------------------------------+ .
- . | | .
- . | A P P L I C A T I O N | .
- . | | .
- . +--------------+---------------+ .
- . | .
- . | .
- . +-------------------+----------------------+ .
- . | : | .
- . | b i n d e r : | .
- . | A F B - D A E M O N : PLUGINS | .
- . | : | .
- . +-------------------+----------------------+ .
- . | .
- . . . . . . . . . . . . | . . . . . . . . . . . . .
- |
- v
- AGL SYSTEM
+<h4><a id="binder-fig-basis">Figure: binder afb-daemon, basis</a></h4>
+
+![binder-basis][binder-basis]
The application and its companion binder run in secured and isolated
environment set for them. Applications are intended to access to AGL
2. It acts as an HTTP server for serving files to HTML5 applications;
3. It allows HTML5 applications to have native extensions subject
-to security enforcement for accessing hardware ressources or
+to security enforcement for accessing hardware resources or
for speeding parts of algorithm.
Use cases of the binder afb-daemon
### Remotely running application
-One of the most interresting aspect of using the binder afb-daemon
+One of the most interesting aspect of using the binder afb-daemon
is the ability to run applications remotely. This feature is
possible because the binder afb-daemon implements native web
protocols.
-So the [figure binder, basis](#binder-fig-1) would become
+So the [figure binder, basis](#binder-fig-basis) would become
when the application is run remotely:
-<a id="binder-fig-remote"><h4>Figure: binder afb-daemon and remotely running application</h4></a>
-
- +------------------------------+
- | |
- | A P P L I C A T I O N |
- | |
- +--------------+---------------+
- |
- ~ ~ ~ ~ ~ ~
- : NETWORK :
- ~ ~ ~ ~ ~ ~
- |
- . . . . . . . . . . . . . . | . . . . . . . . . . . . . .
- . Isolated security | .
- . context | .
- . | .
- . . . . . . . . . . . . . . . . . . . . . . . . . .
- . . . .
- . . F I R E W A L L . .
- . . . .
- . . . . . . . . . . . . . . . . . . . . . . . . . .
- . | .
- . +-------------------+----------------------+ .
- . | : | .
- . | A F B - D A E M O N : PLUGINS | .
- . | : | .
- . +-------------------+----------------------+ .
- . | .
- . . . . . . . . . . . . . . | . . . . . . . . . . . . . .
- |
- v
- AGL SYSTEM
+<h4><a id="binder-fig-remote">Figure: binder afb-daemon and remotely running application</a></h4>
+
### Adding native features to HTML5/QML applications
-Applications can provide with their packaged delivery a plugin.
-That plugin will be instanciated for each application instance.
-The methods of the plugin will be accessible by applications and
-will be excuted within the security context.
+Applications can provide with their packaged delivery a binding.
+That binding will be instantiated for each application instance.
+The methods of the binding will be accessible by applications and
+will be executed within the security context.
### Offering services to the system
It is possible to run the binder afb-daemon as a daemon that provides the
-API of its plugins.
+API of its bindings.
This will be used for:
In that case, the figure showing the whole aspects is
-<a id="binder-fig-remote"><h4>Figure: binder afb-daemon for services</h4></a>
-
- . . . . . . . . . . . . . . . . . . . . . .
- . Isolated security context application .
- . .
- . +------------------------------+ .
- . | | .
- . | A P P L I C A T I O N | .
- . | | .
- . +--------------+---------------+ . . . . . . . . . . . . . . . . . . . . . . .
- . | . . Isolated security context A .
- . | . . .
- . +-----------------+------------------+ . . +------------------------------------+ .
- . | : | . . | : | .
- . | b i n d e r : | . . | b i n d e r : service | .
- . | A F B - D A E M O N : PLUGINS | . . | A F B - D A E M O N : PLUGINS | .
- . | : | . . | : A | .
- . +-----------------+------------------+ . . +-----------------+------------------+ .
- . | . . | .
- . . . . . . . . . . | . . . . . . . . . . . . . . . . . . . . . | . . . . . . . . . . .
- | |
- v v
- ================================================================================
- D - B U S & C Y N A R A
- ================================================================================
- ^ ^
- | |
- . . . . . . . . . . | . . . . . . . . . . . . . . . . . . . . . | . . . . . . . . . . .
- . | . . | .
- . +-----------------+------------------+ . . +-----------------+------------------+ .
- . | : | . . | : | .
- . | b i n d e r : service | . . | b i n d e r : service | .
- . | A F B - D A E M O N : PLUGINS | . . | A F B - D A E M O N : PLUGINS | .
- . | : B | . . | : C | .
- . +------------------------------------+ . . +------------------------------------+ .
- . . . .
- . Isolated security context B . . Isolated security context C .
- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
+<h4><a id="binder-fig-remote">Figure: binder afb-daemon for services</a></h4>
+![afb-for-services][afb-for-services]
For this case, the binder afb-daemon takes care to attribute one single session
-context to each client instance. It allows plugins to store and retrieve data
+context to each client instance. It allows bindings to store and retrieve data
associated to each of its client.
-The plugins of the binder afb-daemon
+The bindings of the binder afb-daemon
------------------------------------
-The binder can instanciate plugins. The primary use of plugins
+The binder can instantiate bindings. The primary use of bindings
is to add native methods that can be accessed by applications
written with any language through web technologies ala JSON RPC.
3. provide customers services
-A specific document explains how to write an afb-daemon binder plugin:
-[HOWTO WRITE a PLUGIN for AFB-DAEMON](afb-plugin-writing.html)
+A specific document explains how to write an afb-daemon binder binding:
+[HOWTO WRITE a BINDING for AFB-DAEMON](afb-bindings-writing.html)
Launching the binder afb-daemon
Increases the verbosity, can be repeated
+ --quiet
+
+ Decreases the verbosity, can be repeated
+
--port=xxxx
HTTP listening TCP port [default 1234]
+ --workdir=xxxx
+
+ Directory where the daemon must run [default: $PWD if defined
+ or the current working directory]
+
+ --uploaddir=xxxx
+
+ Directory where uploaded files are temporarily stored [default: workdir]
+
--rootdir=xxxx
- HTTP Root Directory [default $AFBDIR or else $HOME/.AFB]
+ Root directory of the application to serve [default: workdir]
+
+ --roothttp=xxxx
+
+ Directory of HTTP served files. If not set, files are not served
+ but apis are still accessibles.
--rootbase=xxxx
HTML Root API URL [default /api]
- The plugins are available within that url.
+ The bindings are available within that url.
--alias=xxxx
This option can be repeated.
+ --no-httpd
+
+ Tells to not start the HTTP server.
+
--apitimeout=xxxx
- Plugin API timeout in seconds [default 20]
+ binding API timeout in seconds [default 20]
Defines how many seconds maximum a method is allowed to run.
0 means no limit.
Client cache end of live [default 100000 that is 27,7 hours]
- --sessiondir=xxxx
-
- Sessions file path [default rootdir/sessions]
-
--session-max=xxxx
Maximum count of simultaneous sessions [default 10]
--ldpaths=xxxx
- Load Plugins from given paths separated by colons
- as for dir1:dir2:plugin1.so:... [default = $libdir/afb]
+ Load bindings from given paths separated by colons
+ as for dir1:dir2:binding1.so:... [default = $libdir/afb]
- You can mix path to directories and to plugins.
+ You can mix path to directories and to bindings.
The sub-directories of the given directories are searched
recursively.
- The plugins are the files terminated by '.so' (the extension
+ The bindings are the files terminated by '.so' (the extension
so denotes shared object) that contain the public entry symbol.
- --plugin=xxxx
+ --binding=xxxx
- Load the plugin of given path.
+ Load the binding of given path.
--token=xxxx
If set to the empty string, then any initial token is accepted.
+ --random-token
+
+ Generate a random starting token. See option --exec.
+
--mode=xxxx
Set the mode: either local, remote or global.
Provides a binder afb-daemon service through dbus.
- The name xxxx must be the name of an API defined by a plugin.
+ The name xxxx must be the name of an API defined by a binding.
This API is exported through DBUS.
+ --ws-client=xxxx
+
+ Transparent binding to a binder afb-daemon service through a WebSocket.
+
+ The value of xxxx is either a unix naming socket, of the form "unix:path/api",
+ or an internet socket, of the form "host:port/api".
+
+ --ws-server=xxxx
+
+ Provides a binder afb-daemon service through WebSocket.
+
+ The value of xxxx is either a unix naming socket, of the form "unix:path/api",
+ or an internet socket, of the form "host:port/api".
+
--foreground
Get all in foreground mode (default)
Get all in background mode
+ --no-httpd
+
+ Forbids HTTP serve
+
+ --exec
+
+ Must be the last option for afb-daemon. The remaining
+ arguments define a command that afb-daemon will launch.
+ The sequences @p, @t and @@ of the arguments are replaced
+ with the port, the token and @.
+
+ --tracereq=xxxx
+
+ Trace the processing of requests in the log file.
+
+ Valid values are 'no' (default), 'common', 'extra' or 'all'.
+
+
+
+
Future development of afb-daemon
--------------------------------
- Make the service connection using WebSocket not DBUS.
-- Management of targetted events.
+- Management of targeted events.
-- Securisation of LOA.
+- Securing LOA.
- Integration of the protocol JSON-RPC for the websockets.
-
+[binder-basis]: pictures/AFB_overview.svg
+[afb-for-services]: pictures/AFB_for_services.svg
Code Review / src / app-framework-binder.git / blobdiff