| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
Refactors the IRMd to extract reg_api and irm_flow structures to their
own sources.
Fixes some locking bugs.
|
| |
|
|
|
|
|
|
|
| |
Flow allocation requests and registered api states revised so all
states are tracked with a condition variable. This is a more reliable
approach and improves stability of flow allocation.
Some other refactoring was also done, such as renaming port_map_entry
to irm_flow and hiding some internal structures of the registry.
|
| |
|
|
|
| |
The destroy now only frees after all threads stopped using the object.
Also fixes a SEGV when trying to allocate a flow to a remote name.
|
| |
|
|
|
|
| |
Easier names for the functions.The registry now uses a single list to
keep track of applications (bindings), moved the auto_exec state per
binding.
|
| |
|
|
|
|
|
|
|
|
| |
For locally registered processes, the IRMd will first look for the
local, then the normal, then the shim-udp. It will look for a normal,
a shim-eth-llc and ultimately a shim-udp for non-local destinations.
It does not yet check if a remote destination is actually known in a
DIF.
Fixes #18.
|
| |
|
|
|
| |
Reflects that the functions (dis)associate an application instance
from/with a name and not remove it from the registry entirely.
|
|
|
All registry functionality has been extracted from the IRMd to improve
modularity and legibility of the code.
|
