12 The name **afb-daemon** stands for *Application
13 Framework Binder Daemon*. That is why afb-daemon
14 is also named ***the binder***.
16 **Afb-daemon** is in charge to bind one instance of
17 an application to the AGL framework and AGL system.
19 On the following figure, you can use a typical use
22 <a id="binder-fig-basis"><h4>Figure: binder afb-daemon, basis</h4></a>
24 . . . . . . . . . . . . . . . . . . . . . . . . . .
25 . Isolated security context .
27 . +------------------------------+ .
29 . | A P P L I C A T I O N | .
31 . +--------------+---------------+ .
34 . +-------------------+----------------------+ .
37 . | A F B - D A E M O N : PLUGINS | .
39 . +-------------------+----------------------+ .
41 . . . . . . . . . . . . | . . . . . . . . . . . . .
46 The application and its companion binder run in secured and isolated
47 environment set for them. Applications are intended to access to AGL
48 system through the binder.
50 The binder afb-daemon serves multiple purposes:
52 1. It acts as a gateway for the application to access the system;
54 2. It acts as an HTTP server for serving files to HTML5 applications;
56 3. It allows HTML5 applications to have native extensions subject
57 to security enforcement for accessing hardware ressources or
58 for speeding parts of algorithm.
60 Use cases of the binder afb-daemon
61 ----------------------------------
63 This section tries to give a better understanding of the binder
64 usage through several use cases.
66 ### Remotely running application
68 One of the most interresting aspect of using the binder afb-daemon
69 is the ability to run applications remotely. This feature is
70 possible because the binder afb-daemon implements native web
73 So the [figure binder, basis](#binder-fig-1) would become
74 when the application is run remotely:
76 <a id="binder-fig-remote"><h4>Figure: binder afb-daemon and remotely running application</h4></a>
78 +------------------------------+
80 | A P P L I C A T I O N |
82 +--------------+---------------+
88 . . . . . . . . . . . . . . | . . . . . . . . . . . . . .
89 . Isolated security | .
92 . . . . . . . . . . . . . . . . . . . . . . . . . .
94 . . F I R E W A L L . .
96 . . . . . . . . . . . . . . . . . . . . . . . . . .
98 . +-------------------+----------------------+ .
100 . | A F B - D A E M O N : PLUGINS | .
102 . +-------------------+----------------------+ .
104 . . . . . . . . . . . . . . | . . . . . . . . . . . . . .
109 ### Adding native features to HTML5/QML applications
111 Applications can provide with their packaged delivery a plugin.
112 That plugin will be instanciated for each application instance.
113 The methods of the plugin will be accessible by applications and
114 will be excuted within the security context.
116 ### Offering services to the system
118 It is possible to run the binder afb-daemon as a daemon that provides the
121 This will be used for:
123 1. offering common APIs
125 2. provide application's services (services provided as application)
127 In that case, the figure showing the whole aspects is
129 <a id="binder-fig-remote"><h4>Figure: binder afb-daemon for services</h4></a>
131 . . . . . . . . . . . . . . . . . . . . . .
132 . Isolated security context application .
134 . +------------------------------+ .
136 . | A P P L I C A T I O N | .
138 . +--------------+---------------+ . . . . . . . . . . . . . . . . . . . . . . .
139 . | . . Isolated security context A .
141 . +-----------------+------------------+ . . +------------------------------------+ .
143 . | b i n d e r : | . . | b i n d e r : service | .
144 . | A F B - D A E M O N : PLUGINS | . . | A F B - D A E M O N : PLUGINS | .
145 . | : | . . | : A | .
146 . +-----------------+------------------+ . . +-----------------+------------------+ .
148 . . . . . . . . . . | . . . . . . . . . . . . . . . . . . . . . | . . . . . . . . . . .
151 ================================================================================
152 D - B U S & C Y N A R A
153 ================================================================================
156 . . . . . . . . . . | . . . . . . . . . . . . . . . . . . . . . | . . . . . . . . . . .
158 . +-----------------+------------------+ . . +-----------------+------------------+ .
160 . | b i n d e r : service | . . | b i n d e r : service | .
161 . | A F B - D A E M O N : PLUGINS | . . | A F B - D A E M O N : PLUGINS | .
162 . | : B | . . | : C | .
163 . +------------------------------------+ . . +------------------------------------+ .
165 . Isolated security context B . . Isolated security context C .
166 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
169 The plugins of the binder afb-daemon
170 ------------------------------------
172 The binder can instanciate plugins. The primary use of plugins
173 is to add native methods that can be accessed by applications
174 written with any language through web technologies ala JSON RPC.
176 This simple idea is declined to serves multiple purposes:
178 1. add native feature to applications
180 2. add common API available by any applications
182 3. provide customers services
184 A specific document shows