Ouroboros main repository http://www.ouroboros.rocks/cgit/ouroboros/atom?h=0.3 2016-10-26T09:52:53Z 2016-10-26T09:52:53Z Sander Vrijders sander.vrijders@intec.ugent.be 2016-10-25T11:22:51Z urn:sha1:f0646875d0bc941e339d305d0c68b13543cd6f2a This adds the ability to query IPCPs if a name can be reached through them, e.g. if a name is available in a DIF. This means that in the shim-udp a DNS query is performed, in the shim-eth-llc an ARP-like query has been added, in the local a check is done to see if the name is registered, and in the normal currently no application is reachable through it. 2016-08-21T16:32:12Z dimitri staessens dimitri.staessens@intec.ugent.be 2016-08-20T08:42:36Z urn:sha1:0efb1ff527ce3fb50d4c72c02904fa1cdd1e3a66 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. 2016-08-08T19:15:57Z dimitri staessens dimitri.staessens@intec.ugent.be 2016-08-08T19:15:57Z urn:sha1:18e440197cae6d537765a4de6a915f074dce4de5 Refactors the IRMd to extract reg_api and irm_flow structures to their own sources. Fixes some locking bugs. 2016-07-27T13:55:54Z dimitri staessens dimitri.staessens@intec.ugent.be 2016-07-27T13:29:28Z urn:sha1:0dda754f6eb91af15f7c69523e2ebb627086b457 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. 2016-07-15T13:49:23Z dimitri staessens dimitri.staessens@intec.ugent.be 2016-07-15T13:49:23Z urn:sha1:e14d0da88d4f3fcd0c19c231b59d31189c4d71ad 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. 2016-07-11T08:47:57Z dimitri staessens dimitri.staessens@intec.ugent.be 2016-07-09T13:38:31Z urn:sha1:93ed0b44a196d43771a6df24831db4ba3a60ef1b 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. 2016-07-07T18:54:06Z dimitri staessens dimitri.staessens@intec.ugent.be 2016-07-07T17:01:00Z urn:sha1:27b36b690a4b048721f0a568ef0aff03bf8e9855 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. 2016-07-06T09:33:25Z dimitri staessens dimitri.staessens@intec.ugent.be 2016-07-06T09:33:25Z urn:sha1:f437a4a122614a01a1f97713ddc6e45c1011b86f Reflects that the functions (dis)associate an application instance from/with a name and not remove it from the registry entirely. 2016-07-05T15:05:08Z dimitri staessens dimitri.staessens@intec.ugent.be 2016-07-05T14:38:54Z urn:sha1:72469bafa9d81a5578f53ec40175001f4c77cff6 All registry functionality has been extracted from the IRMd to improve modularity and legibility of the code.