Developpers of HTML5 applications (client side) can easyly create applications for AGL framework using their prefered @@ -51,7 +58,7 @@ with the current x-afb-json1 protocol.
-Writing Qt applications is also possible because Qt offers APIs to make HTTP queries and to connect using WebSockets.
@@ -66,7 +73,7 @@ a simple “hello world” application in QML -C applications can use the binder afb-daemon through a websocket connection.
@@ -85,8 +92,8 @@ and being less dependant of libsystemd.Applications must be aware of the the features session and token +when they interact with the binder afb-daemon.
Applications are communicating with their binder afb-daemon using a network connection or a kind of network connection (unix domain @@ -95,12 +102,25 @@ Also, HTTP protocol is not a connected protocol. It means that the socket connection can not be used to authenticate a client.
For this reason, the binder should authenticate the application -by using a commonly shared secret named token.
- -At start, the framework communicate a common secret to both the binder -and its client: the application. When the application
+by using a commonly shared secret named token and the identification +of the client named session.Plugins and features of the binder need to keep track of the client +instances. In principle, a binder afb-daemon is launched by application +instance. But for services, a binder
+ + +At start, the framework communicate a common secret to both the binder +and its client: the application. This initial secret is the +initial token.
+ +For each of its client application, the binder manages a current active +token. The initial token is the default active token. It is the expected +token for new clients.