The binder provides the way to connect applications to the services that it needs.

It provides a fast way to securely offer APIs to applications written in any language and running almost anywhere.

The word daemon, here, denote the fact that the binder makes witchcraft to connect applications to their expected services. (note: that usually the term of daemon denotes background process but not here).

Each binder afb-daemon is in charge to bind one instance of an application or service to the rest of the system, applications and services. Within AGL, the connection between services and/or applications is tuned by the AGL framework and the AGL system.

The basis of the binder

The following figure shows main concepts linked to the binder.

Figure: binder basis

The shown elements are:

Interconnection of binders

The AGL framework interprets the widget/application manifests to setup the bindings configuration of the binders.

The figure below shows that binders are interconnected.

Figure: binder interconnection

The figure shows 4 several application/service: A, B, C and D.

The application A might use an API that is shown as a local binding but that in reality runs within the context of D.

The framework AGL takes care of making the plumbing working.