irmd, lib: Rebuild the IRMd data model

The complete data model inside the IRMd has been restructured. The
bind operation was revised to allow binding of AP and AP instances and
register those names with different DIFs (see "irm bind" for details).

Server applications require to call ap_init with a server name
argument, client application that do not the be reachable over any DIF
can call ap_init(NULL). Calling ap_init for a client with a specified
name will not have adverse consequences for the application, but will
consume unnecessary resources in the IRMd.

Application servers can now be started at any point after the IRMd has
been started. Starting servers, binding AP names and registering names in
DIFs can be performed in any order that does not defy temporal logic.

Supports naming instances by their pid. In case of IPCP Instances
created with the IRM tool, the name assigned during "irm ipcp create"
can be used.

All the changes required updates in the tools.

1 files changed, 2 insertions, 2 deletions

diff --git a/src/tools/irm/irm.c b/src/tools/irm/irm.c
index 14420207..c260feb9 100644
--- a/src/tools/irm/irm.c
+++ b/src/tools/irm/irm.c
@@ -46,8 +46,8 @@ static const struct cmd {
         int (* func)(int argc, char ** argv);
 } cmds[] = {
         { "ipcp",            ipcp_cmd },
-        { "bind",            do_bind },
-        { "unbind",          do_unbind },
+        { "bind",            bind_cmd },
+        { "unbind",          unbind_cmd },
         { "register",        do_register },
         { "unregister",      do_unregister },
         { "help",            do_help },