Fedora 30 packaging fix issu

[src/app-framework-binder.git] / docs / afb-daemon-vocabulary.md

diff --git a/docs/afb-daemon-vocabulary.md b/docs/afb-daemon-vocabulary.md
index 6c51f12..d28699b 100644 (file)
--- a/docs/afb-daemon-vocabulary.md
+++ b/docs/afb-daemon-vocabulary.md
@@ -3,15 +3,15 @@
 ## Binding
 
 A shared library object intended to add a functionality to an afb-daemon
-instance.  
+instance.
 It implements an API and may provide a service.
 
-Binding made for services can have specific entry point called after
+Binding made for services can have specific entry points called after
 initialization and before serving.
 
 ## Event
 
-Message with data propagated from the services to the client and not expecting
+Messages with data propagated from the services to the client and not expecting
 any reply.
 
 The current implementation allows to widely broadcast events to all clients.
@@ -24,10 +24,6 @@ assurance that the services can expect from the session.
 The exact definition of the meaning of these levels and how to use it remains to
 be achieved.
 
-## Plugin
-
-Old name for binding, see binding.
-
 ## Request
 
 A request is an invocation by a client to a binding method using a message
@@ -35,7 +31,6 @@ transferred through some protocol:
 
 - HTTP
 - WebSocket
-- DBUS
 - ...
 
 and served by ***afb-daemon***
@@ -46,23 +41,26 @@ This is a message sent to client as the result of the request.
 
 ## Service
 
-Service are made of bindings running by their side on their binder.  
-It can serve many client.  
-Each one attached to one session.
+Service are made of bindings running on a binder
+The binder is in charge of connecting services and applications.
+A service can serve many clients.
+
+The framework establishes connection between the services and the clients.
+Using sockets currently but other protocols are considered.
 
-The framework establishes connection between the services and the clients.  
-Using DBus currently but other protocols are considered.
+The term of service is tightly bound to the notion of API.
 
 ## Session
 
 A session is meant to be the unique instance context of a client,
 which identify that instance across requests.
 
-Each session has an identifier.  
+Each session has an identifier.
 Session identifier generated by afb-daemon are UUIDs.
+A client can present its own session id.
 
-Internally, afb-daemon offers a mechanism to attach data to sessions.  
-When the session is closed or disappears, the data attached to that session
+Internally, afb-daemon offers a mechanism to attach data to sessions.
+When a session is closed or disappears, data attached to that session
 are freed.
 
 ## Token