Client library for creating integrations against DDMW.
- sending commands and receiving replies.
- ask the server who owns the connection.
connect method supports optionally authenticating the connection, but
this can also be performed explicitly after the connection has been
established using the
Most, if not all, DDMW applications will require a few common configuration
parameters. To this end a common configuration format is specified in the
conf module. There’s a helper function for loading and parsing such a
The configuration file is entirely optional, but it provides a common configuration file structure for applications to use.
The DDMW servers’ client interfaces support a few common commands which
are typically used to simply for low-level availability checks and for
quering the servers for static information. The
probe module contains
helper functions for accessing this type of data.
The primary role of integrations such as native DDMW applications or
proxies is to send and receiver messages or streams. The
strm modules provide functions for sending and receiving messages and
To create management clients the
mgmt module wrapper contains helper
functions for management commands.
Authentication and unauthentication.
DDMW client applications (including proxies) will contain common configuration parameters. This module is used to provide a defacto-standard interface and layout for loading client configuration parameters.
Methods used to establish connections to DDMW Core servers’ client interfaces.
Collection of management helper modules.
Message sending and receiving functions.
Core node inspection functions.
Stream sending and receiving functions.
Various types used when communicating with core servers.