Binding lists are generated by the mk tools (i.e., mkapp and mksys) and are installed into the "system" configuration tree by the installer. They are in the "system" tree to keep them protected from sandboxed applications.

Bindings between clients and servers are stored under the client's configuration. If the client is an application, the bindings are stored under the application's configuration in the "system" tree. If the client is a non-application user, the bindings are stored under the "/users/bindings" branch of the "system" tree.

system:/
    apps/
        <app name>/
            bindings/
                <client interface name>
                        app         <string>
                        user        <string>
                        interface   <string>
    users/
        <user name>/
            bindings/
                <client interface name>
                        app         <string>
                        user        <string>
                        interface   <string>

Each <client interface name> corresponds to an IPC interface required by a component (listed in the api: subsection of a requires: section in the component's Component.cdef file).

Either app or user must exist, but never both.

The app is the name of the application that will run the server on the target.

The user is the name of the user account that will run the server on the target.

The interface name corresponds to the server IPC interface name.

Note: Changing the binding configuration in the configuration tree does not automatically result in changes to the actual IPC bindings that are in effect in the Service Directory. The sdir implements a load command that can be used to update the Service Directory with the latest binding configuration from the configuration tree.

Copyright (C) Sierra Wireless Inc. Use of this work is subject to license.