Add the external binding feature

[src/app-framework-main.git] / docs / 2.2-config.xml.md

diff --git a/docs/2.2-config.xml.md b/docs/2.2-config.xml.md
index a7f32dc..39ea23d 100644 (file)
--- a/docs/2.2-config.xml.md
+++ b/docs/2.2-config.xml.md
@@ -156,7 +156,7 @@ The name is the name of the required API.
 The value describes how to connect to the required api.  
 It is either:
 
-- local:  
+- local: OBSOLETE, PROVIDED FOR COMPATIBILITY 
   The binding is a local shared object.  
   In that case, the name is the relative path of the
   shared object to be loaded.
@@ -171,14 +171,33 @@ It is either:
 - dbus:  
   The framework connect using internal dbus
 
-- link:  
- The framework connect in memory by dynamically linking
-
 - cloud: [PROPOSAL - NOT IMPLEMENTED]  
   The framework connect externally using websock.  
   In that case, the name includes data to access the service.  
   Example: `<param name="log:https://oic@agl.iot.bzh/cloud/log" value="cloud" />`
 
+#### required-binding: param name=[name or path]
+
+The name or the path of the required BINDING.
+
+The value describes how to connect to the required binding.
+It is either:
+
+- local:
+  The binding is a local shared object.  
+  In that case, the name is the relative path of the
+  shared object to be loaded.
+
+- extern:
+  The binding is external. The name is the exported binding name.
+  See provided-binding.
+
+#### provided-binding: param name=[exported name]
+
+Exports a local binding to other applications.
+
+The value must contain the path to the exported binding.
+
 ### required-permission: feature name="urn:AGL:widget:required-permission"
 
 List of the permissions required by the unit.