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 instanciated for each application instance. The methods of the binding will be accessible by applications and will be excuted within the security context.
It is possible to run the binder afb-daemon as a daemon that provides the API of its plugins.
+It is possible to run the binder afb-daemon as a daemon that provides the API of its bindings.
offering common APIs
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 associated to each of its client.
-The plugins of the binder afb-daemon
-The binder can instanciate plugins. The primary use of plugins is to add native methods that can be accessed by applications written with any language through web technologies ala JSON RPC.
+For this case, the binder afb-daemon takes care to attribute one single session context to each client instance. It allows bindings to store and retrieve data associated to each of its client.
+The bindings of the binder afb-daemon
+The binder can instanciate 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.
This simple idea is declined to serves multiple purposes:
add native feature to applications
add common API available by any applications
provide customers services
-A specific document explains how to write an afb-daemon binder plugin: HOWTO WRITE a PLUGIN for AFB-DAEMON
+A specific document explains how to write an afb-daemon binder binding: HOWTO WRITE a BINDING for AFB-DAEMON
Launching the binder afb-daemon
The launch options for binder afb-daemon are:
--help
@@ -209,7 +209,7 @@ Figure: binder afb-daemon for services
HTML Root API URL [default /api]
- The plugins are available within that url.
+ The bindings are available within that url.
--alias=xxxx
@@ -224,7 +224,7 @@ Figure: binder afb-daemon for services
--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.
@@ -247,19 +247,19 @@ Figure: binder afb-daemon for services
--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
@@ -294,7 +294,7 @@ Figure: binder afb-daemon for services
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.
--foreground