|
DTNMA Reference Tools v2.2.0 - 14.ge930b04
Delay-Tolerant Networking Management Architecture (DTNMA) Tool Suite
|
This library is subdivided into the following subsystems, each with a corresponding directory in the source tree and include tree. The library files are all under the The CACE Library topic.
The cace/util directory contains common utility preprocessor defines, functions, etc. used by other areas of this project. The specific header cace/util/logging.h deals with Logging which is used by all libraries and executables of the project.
The cace/ari directory and CACE ARI Processing topic deals with the ARI data model and encoding / decoding (CODEC) functions related to processing ARI values. There is also a top-level include cace/ari.h which includes all other headers dealing with ARI handling.
The type cace_ari_t is the API focal point for this library. There are related algorithmic types and functions like cace_ari_visit() and cace_ari_translate() defined here.
The cace/amm directory and CACE AMM Processing topic deals with aspects of the AMM such as the abstract object structure and value typing subsystem. Types within the AMM extend beyond the built-in types of ARI values into "semantic types" as defined in Section 3.3 of the AMM [6].
The type cace_amm_obj_store_t is used to register and lookup abstract AMM object handles, which used within the Reference DTNMA Agent for state keeping. There are related algorithmic types and functions like cace_amm_lookup_deref() for object dereferencing and cace_amm_actual_param_set_populate() for parameter handling.
The type cace_amm_type_t is used to represent both built-in ARI types as well as different forms of semantic typing built upon the built-in types. There are related algorithmic functions like cace_amm_type_match() and cace_amm_type_convert defined here.
The cace/amp directory and CACE AMP Processing topic deals with ARI values encoded in binary form into AMP messages This includes POSIX socket utilities used by the refda-socket and refdm-socket daemons as a reference to what an AMP transport binding should look like and how it should behave.