@@ -134,24 +134,32 @@ This is a debug message issued when the DHCP-DDNS application encountered an
error while decoding a response to DNS Update message. Typically, this error
will be encountered when a response message is malformed.
% DHCP_DDNS_NCR_UDP_LISTEN_CLOSE application encountered an error while closing the UDP socket used to receive NameChangeRequests : %1
% DHCP_DDNS_NCR_LISTEN_CLOSE_ERROR application encountered an error while closing the the listener used to receive NameChangeRequests : %1
This is an error message that indicates the application was unable to close the
UDP socket being used to receive NameChangeRequests. Socket closure may occur
listener connection used to receive NameChangeRequests. Closure may occur
during the course of error recovery or duing normal shutdown procedure. In
either case the error is unlikely to impair the application's ability to
process requests but it should be reported for analysis.
% DHCP_DDNS_NCR_UDP_RECV_ERROR UDP socket receive error while listening for DNS Update requests: %1
This is an error message indicating that an IO error occured while listening
over a UDP socket for DNS update requests. in the request. This could indicate
a network connectivity or system resource issue.
% DHCP_DDNS_NCR_RECV_NEXT application could not initiate the next read following
a request receive.
This is a error message indicating that NameChangeRequest listener could not start another read after receiving a request. While possible, this is highly unlikely and is probably a programmatic error. The application should recover on its
own.
% DHCP_DDNS_NCR_UDP_SEND_CLOSE application encountered an error while closing the UDP socket used to send NameChangeRequests : %1
% DHCP_DDNS_NCR_SEND_CLOSE_ERROR DHCP-DDNS client encountered an error while closing ththe sender connection used to send NameChangeRequests : %1
This is an error message that indicates the DHCP-DDNS client was unable to close
the UDP socket being used to send NameChangeRequests. Socket closure may occur
during the course of error recovery or duing normal shutdown procedure. In
either case the error is unlikely to impair the client's ability to send
requests but it should be reported for analysis.
the connection used to send NameChangeRequests. Closure may occur during the
course of error recovery or duing normal shutdown procedure. In either case
the error is unlikely to impair the client's ability to send requests but it
should be reported for analysis.
% DHCP_DDNS_NCR_SEND_NEXT DHCP-DDNS client could not initiate the next request send following send completion.
This is a error message indicating that NameChangeRequest sender could not start another send after completing the send of the previous request. While possible, this is highly unlikely and is probably a programmatic error. The application should recover on its own.
% DHCP_DDNS_NCR_UDP_RECV_ERROR UDP socket receive error while listening for DNS Update requests: %1
This is an error message indicating that an IO error occured while listening
over a UDP socket for DNS update requests. This could indicate a network
connectivity or system resource issue.
% DHCP_DDNS_NO_MATCH No DNS servers match FQDN: %1
This is warning message issued when there are no domains in the configuration
/// @brief This file defines abstract classes for exchanging NameChangeRequests.
///
/// These classes are used for sending and receiving requests to update DNS
/// information for FQDNs embodied as NameChangeRequests (aka NCRs). Ultimately,/// NCRs must move through the following three layers in order to implement
/// information for FQDNs embodied as NameChangeRequests (aka NCRs). Ultimately,
/// NCRs must move through the following three layers in order to implement
/// DHCP-DDNS:
///
/// * Application layer - the business layer which needs to
/// transport NameChangeRequests, and is unaware of the means by which
/// they are transported.
///
/// * IO layer - the low-level layer that is directly responsible for
/// sending and receiving data asynchronously and is supplied through
/// other libraries. This layer is largely unaware of the nature of the
/// data being transmitted. In other words, it doesn't know beans about
/// NCRs.
///
/// * NameChangeRequest layer - This is the layer which acts as the
/// intermediary between the Application layer and the IO layer. It must
/// be able to move NameChangeRequests to the IO layer as raw data and move
/// raw data from the IO layer in the Application layer as
/// NameChangeRequests.
///
/// The abstract classes defined here implement implement the latter, middle
/// layer, the NameChangeRequest layer. There are two types of participants
/// in this middle ground:
/// * IO layer - the low-level layer that is directly responsible for
/// sending and receiving data asynchronously and is supplied through
/// other libraries. This layer is largely unaware of the nature of the
/// data being transmitted. In other words, it doesn't know beans about
/// NCRs.
///
/// The abstract classes defined here implement the latter, middle layer,
/// the NameChangeRequest layer. There are two types of participants in this
/// middle ground:
///
/// * listeners - Receive NCRs from one or more sources. The DHCP-DDNS
/// application, (aka D2), is a listener. Listeners are embodied by the
...
...
@@ -65,7 +66,7 @@
namespaceisc{
namespaced2{
/// @brief Exception thrown if an NcrListenerError occurs.
/// @brief Exception thrown if an NcrListenerError encounters a general error.
