/*
 * SPDX-FileCopyrightText: 2012 Copyright contributors to the cppTango project
 *
 * SPDX-License-Identifier: LGPL-3.0-or-later
 */

#ifndef TANGO_INTERNAL_DOXYGEN_DEFINES_H
#define TANGO_INTERNAL_DOXYGEN_DEFINES_H

#include <vector>

// NOTE: This file gets rendered by doxygen as a series of html files in the top
// level directory.  The scripts to build the multi-version site in ci/docs-site
// assume that all the html files will be in the top level, therefore, if you
// change things so that the site contains subdirectories, this will require
// updating the process we use for building the multi-version site to account
// for this.

/**
\file   doxygen_defines.h
\brief Just a file to write some Doxygen specific documentation
*/

/**@typedef DbData
 * A vector of DbDatum class
 */
typedef std::vector<DbDatum> DbData;
/**@typedef DbDevInfos
 * A vector of DbDevInfo structure
 */
typedef std::vector<DbDevInfo> DbDevInfos;
/**@typedef DbDevExportInfos
 * A vector of DbDevExport structure
 */
typedef std::vector<DbDevExportInfo> DbDevExportInfos;
/**@typedef DbDevImportInfos
 * A vector of DbDevImport structure
 */
typedef std::vector<DbDevImportInfo> DbDevImportInfos;

/**@typedef CommandInfoList
 * A vector of CommandInfo structure
 */
typedef std::vector<CommandInfo> CommandInfoList;
/**@typedef AttributeInfoList
 * A vector of AttributeInfo structure
 */
typedef std::vector<AttributeInfo> AttributeInfoList;
/**@typedef AttributeInfoListEx
 * A vector of AttributeInfoEx structure
 */
typedef std::vector<AttributeInfoEx> AttributeInfoListEx;

/*******************************************************
 *                                                     *
 *               The main page                         *
 *                                                     *
 *******************************************************/

/*! \mainpage
 *
 * \section intro_sec Introduction
 *
 * This is the reference documentation for all classes provided by the Tango C++ API.
 * These classes are divided in two groups (modules) which are
 * \li \ref Client
 * \li \ref Server
 *
 * Client classes are mostly used in application(s) acting as clients and dealing with Tango devices.
 * Server classes are mostly used in Tango class or device server process main function.
 *
 * See the \ref news for details about what's new in the Tango \tangoversion release.
 *
 * In order to develop Tango's related software, it's a good idea to have a look at the
 * <a href=https://tango-controls.readthedocs.io>Tango Controls documentation</a>, especially the
 * <i>Developer's Guide</i> section.
 *
 * A look at the so-called <a href=pages.html>"Related Pages"</a> could also help the developer.
 *
 * Useful information is also available on the <a href=http://www.tango-controls.org>Tango Web site</a>.
 *
 */

/*******************************************************
 *                                                     *
 *          The News page                              *
 *                                                     *
 *******************************************************/

/*! \page news Tango \tangoversion Release Notes
 *
 * \include{doc} RELEASE_NOTES.md
 *
 */

/*******************************************************
 *                                                     *
 *               The Exception related page            *
 *                                                     *
 *******************************************************/

/** @page except Exception
 *
 *
 * @section Ex Tango API exceptions
 * All the exception thrown by this API are Tango::DevFailed exception. This exception is a variable length
 * array of Tango::DevError type. The Tango::DevError type is a four fields structure. These fields are :
 * @li A string describing the error type. This string replaces an error code and allows a more easy management
 * of include files. This field is called @b reason
 * @li A string describing in plain text the reason of the error. This field is called @b desc
 * @li A string giving the name of the method which thrown the exception. This field is named @b origin
 * @li The error severity. This is an enumeration with three values which are WARN, ERR or PANIC. Its
 * name is @b severity
 *
 * This is a variable length array in order to transmit to the client what is the primary error reason. The
 * sequence element 0 describes the primary error. An exception class hierarchy has been implemented within
 * the API to ease API programmers task. All the exception classes inherits from the Tango::DevFailed class.
 * Except for the NamedDevFailedList exception class, they don’t add any new fields to the exception, they
 * just allow easy "catching". Exception classes thrown only by the API layer are :
 * @li ConnectionFailed
 * @li CommunicationFailed
 * @li WrongNameSyntax
 * @li NonDbDevice
 * @li WrongData
 * @li NonSupportedFeature
 * @li AsynCall
 * @li AsynReplyNotArrived
 * @li EventSystemFailed
 * @li NamedDevFailedList
 * @li DeviceUnlocked
 *
 * On top of these classes, exception thrown by the device (Tango::DevFailed exception) are directly passed
 * to the client.
 * @subsection ConFailed The ConnectionFailed exception
 * This exception is thrown when a problem occurs during the connection establishment between the application
 * and the device. The API is stateless. This means that DeviceProxy constructors filter most of the
 * exception except for cases described in the following table.
 * <TABLE>
 * <TR>
 *    <TH style="text-align:center">Method name</TH>
 *    <TH style="text-align:center">device type</TH>
 *    <TH style="text-align:center">error type</TH>
 *    <TH style="text-align:center">Level</TH>
 *    <TH style="text-align:center">reason</TH>
 * </TR>
 * <TR>
 *    <TD style="text-align:center" ROWSPAN=8>DeviceProxy constructor</TD>
 *    <TD style="text-align:center" ROWSPAN=4>with database</TD>
 *    <TD style="text-align:center">TANGO_HOST not set</TD>
 *    <TD style="text-align:center">0</TD>
 *    <TD style="text-align:center">API_TangoHostNotSet</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center" ROWSPAN=3>Device not defined in db or Alias not defined in db</TD>
 *    <TD style="text-align:center">0</TD>
 *    <TD style="text-align:center">DB_DeviceNotDefined</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center">1</TD>
 *    <TD style="text-align:center">API_CommandFailed</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center">2</TD>
 *    <TD style="text-align:center">API_DeviceNotDefined</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center" ROWSPAN=2>with database specified in dev name</TD>
 *    <TD style="text-align:center" ROWSPAN=2>database server not running</TD>
 *    <TD style="text-align:center">0</TD>
 *    <TD style="text-align:center">API_CorbaException</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center">1</TD>
 *    <TD style="text-align:center">API_CantConnectToDatabase</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center" ROWSPAN=2>without database</TD>
 *    <TD style="text-align:center" ROWSPAN=2>Server running but device not defined in server</TD>
 *    <TD style="text-align:center">0</TD>
 *    <TD style="text-align:center">API_CorbaException</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center">1</TD>
 *    <TD style="text-align:center">API_DeviceNotExported</TD>
 * </TR>



 * <TR>
 *    <TD style="text-align:center" ROWSPAN=9>AttributeProxy constructor</TD>
 *    <TD style="text-align:center" ROWSPAN=7>with database</TD>
 *    <TD style="text-align:center">TANGO_HOST not set</TD>
 *    <TD style="text-align:center">0</TD>
 *    <TD style="text-align:center">API_TangoHostNotSet</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center" ROWSPAN=3>Device not defined in db</TD>
 *    <TD style="text-align:center">0</TD>
 *    <TD style="text-align:center">DB_DeviceNotDefined</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center">1</TD>
 *    <TD style="text-align:center">API_CommandFailed</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center">2</TD>
 *    <TD style="text-align:center">API_DeviceNotDefined</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center" ROWSPAN=3>Alias not defined in db</TD>
 *    <TD style="text-align:center">0</TD>
 *    <TD style="text-align:center">DB_SQLError</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center">1</TD>
 *    <TD style="text-align:center">API_CommandFailed</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center">2</TD>
 *    <TD style="text-align:center">API_AliasNotDefined</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center" ROWSPAN=2>with database specified in dev name</TD>
 *    <TD style="text-align:center" ROWSPAN=2>database server not running</TD>
 *    <TD style="text-align:center">0</TD>
 *    <TD style="text-align:center">API_CorbaException</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center">1</TD>
 *    <TD style="text-align:center">API_CantConnectToDatabase</TD>
 * </TR>



 * <TR>
 *    <TD style="text-align:center" ROWSPAN=7>DeviceProxy or AttributeProxy method call (except command_inout,
 read_attribute)</TD>
 *    <TD style="text-align:center" ROWSPAN=2>without database</TD>
 *    <TD style="text-align:center" ROWSPAN=2>Server not running</TD>
 *    <TD style="text-align:center">0</TD>
 *    <TD style="text-align:center">API_CorbaException</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center">1</TD>
 *    <TD style="text-align:center">API_ServerNotRunning</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center" ROWSPAN=5>with database</TD>
 *    <TD style="text-align:center">Server ot running</TD>
 *    <TD style="text-align:center">0</TD>
 *    <TD style="text-align:center">API_DeviceNotExported</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center" ROWSPAN=2>Dead server</TD>
 *    <TD style="text-align:center">0</TD>
 *    <TD style="text-align:center">API_CorbaException</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center">1</TD>
 *    <TD style="text-align:center">API_CantConnectToDevice</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center" ROWSPAN=2>Dead database server when reconnection needed</TD>
 *    <TD style="text-align:center">0</TD>
 *    <TD style="text-align:center">API_CorbaException</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center">1</TD>
 *    <TD style="text-align:center">API_CantConnectToDatabase</TD>
 * </TR>


 * <TR>
 *    <TD style="text-align:center" ROWSPAN=11>DeviceProxy command_inout and read_attribute or AttributeProxy read and
 write</TD>
 *    <TD style="text-align:center" ROWSPAN=3>without database</TD>
 *    <TD style="text-align:center" ROWSPAN=3>Server not running</TD>
 *    <TD style="text-align:center">0</TD>
 *    <TD style="text-align:center">API_DeviceNotExported</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center">1</TD>
 *    <TD style="text-align:center">API_ServerNotRunning</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center">2</TD>
 *    <TD style="text-align:center">API_CommandFailed</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center" ROWSPAN=8>with database</TD>
 *    <TD style="text-align:center" ROWSPAN=2>Server not running</TD>
 *    <TD style="text-align:center">0</TD>
 *    <TD style="text-align:center">API_DeviceNotExported</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center">1</TD>
 *    <TD style="text-align:center">API_CommandFailed</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center" ROWSPAN=3>Dead server</TD>
 *    <TD style="text-align:center">0</TD>
 *    <TD style="text-align:center">API_CorbaException</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center">1</TD>
 *    <TD style="text-align:center">API_CantConnectToDevice</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center">2</TD>
 *    <TD style="text-align:center">API_CommandFailed or API_AttributeFailed</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center" ROWSPAN=3>Dead database server when re-connection needed</TD>
 *    <TD style="text-align:center">0</TD>
 *    <TD style="text-align:center">API_DeviceNotExported</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center">1</TD>
 *    <TD style="text-align:center">API_CantConnectToDatabase</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center">2</TD>
 *    <TD style="text-align:center">API_CommandFailed</TD>
 * </TR>
 * </TABLE>
 * The desc DevError structure field allows a user to get more precise information. These informations
 * are (according to the reason field) :
 * @li @b DB_DeviceNotDefined: The name of the device not defined in the database
 * @li @b API_CommandFailed: The device and command name
 * @li @b API_CantConnectToDevice: The device name
 * @li @b API_CorbaException: The name of the CORBA exception, its reason, its locality, its completed flag and
 * its minor code
 * @li @b API_CantConnectToDatabase: The database server host and its port number
 * @li @b API_DeviceNotExported: The device name
 *
 * @subsection CommFailed The CommunicationFailed exception
 * This exception is thrown when a communication problem is detected during the communication between
 * the client application and the device server. It is a two levels Tango::DevError structure. In case of time-out,
 * the DevError structures fields are:
 * <TABLE>
 * <TR>
 *    <TH style="text-align:center">Level</TH>
 *    <TH style="text-align:center">Reason</TH>
 *    <TH style="text-align:center">Desc</TH>
 *    <TH style="text-align:center">Severity</TH>
 * </TR>
 * <TR>
 *    <TD style="text-align:center">0</TD>
 *    <TD style="text-align:center">API_CorbaException</TD>
 *    <TD style="text-align:center">CORBA exception fields translated into a string</TD>
 *    <TD style="text-align:center">ERR</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center">1</TD>
 *    <TD style="text-align:center">API_DeviceTimedOut</TD>
 *    <TD style="text-align:center">String with time-out value and device name</TD>
 *    <TD style="text-align:center">ERR</TD>
 * </TR>
 * </TABLE>
 * For all other communication errors, the DevError structures fields are:
 * <TABLE>
 * <TR>
 *    <TH style="text-align:center">Level</TH>
 *    <TH style="text-align:center">Reason</TH>
 *    <TH style="text-align:center">Desc</TH>
 *    <TH style="text-align:center">Severity</TH>
 * </TR>
 * <TR>
 *    <TD style="text-align:center">0</TD>
 *    <TD style="text-align:center">API_CorbaException</TD>
 *    <TD style="text-align:center">CORBA exception fields translated into a string</TD>
 *    <TD style="text-align:center">ERR</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center">1</TD>
 *    <TD style="text-align:center">API_CommunicationFailed</TD>
 *    <TD style="text-align:center">String with device, method, command/attribute name</TD>
 *    <TD style="text-align:center">ERR</TD>
 * </TR>
 * </TABLE>
 *
 * @subsection WrongName The WrongNameSyntax exception
 * This exception has only one level of Tango::DevError structure. The possible value for the reason field are :
 * @li @b API_UnsupportedProtocol This error occurs when trying to build a DeviceProxy or an AttributeProxy
 * instance for a device with an unsupported protocol. Refer to the appendix on device naming syntax
 * to get the list of supported database modifier
 * @li @b API_UnsupportedDBaseModifier This error occurs when trying to build a DeviceProxy or an AttributeProxy
 * instance for a device/attribute with a database modifier unsupported. Refer to the appendix on device
 * naming syntax to get the list of supported database modifier
 * @li @b API_WrongDeviceNameSyntax This error occurs for all the other error in device name syntax. It is
 * thrown by the DeviceProxy class constructor.
 * @li @b API_WrongAttributeNameSyntax This error occurs for all the other error in attribute name syntax. It is
 * thrown by the AttributeProxy class constructor.
 * @li @b API_WrongWildcardUsage This error occurs if there is a bad usage of the wildcard character
 *
 * @subsection NonDb The NonDbDevice exception
 * This exception has only one level of Tango::DevError structure. The reason field is set to API_NonDatabaseDevice.
 * This exception is thrown by the API when using the DeviceProxy or AttributeProxy class database access
 * for non-database device.
 *
 * @subsection WrongData The WrongData exception
 * This exception has only one level of Tango::DevError structure. The possible value for the reason field are :
 * @li @b API_EmptyDbDatum This error occurs when trying to extract data from an empty DbDatum object
 * @li @b API_IncompatibleArgumentType This error occurs when trying to extract data with a type different than
 * the type used to send the data
 * @li @b API_EmptyDeviceAttribute This error occurs when trying to extract data from an empty DeviceAttribute
 * object
 * @li @b API_IncompatibleAttrArgumentType This error occurs when trying to extract attribute data with a type
 * different than the type used to send the data
 * @li @b API_EmptyDeviceData This error occurs when trying to extract data from an empty DeviceData object
 * @li @b API_IncompatibleCmdArgumentType This error occurs when trying to extract command data with a
 * type different than the type used to send the data
 *
 * @subsection NonSupported The NonSupportedFeature exception
 * This exception is thrown by the API layer when a request to a feature implemented in Tango device interface
 * release n is requested for a device implementing Tango device interface n-x. There is one possible value
 * for the reason field which is API_UnsupportedFeature.
 *
 * @subsection AsynCall The AsynCall exception
 * This exception is thrown by the API layer when a the asynchronous model id badly used. This exception
 * has only one level of Tango::DevError structure. The possible value for the reason field are :
 * @li @b API_BadAsynPollId This error occurs when using an asynchronous request identifier which is not valid
 * any more.
 * @li @b API_BadAsyn This error occurs when trying to fire callback when no callback has been previously registered
 * @li @b API_BadAsynReqType This error occurs when trying to get result of an asynchronous request with
 * an asynchronous request identifier returned by a non-coherent asynchronous request (For instance,
 * using the asynchronous request identifier returned by a command_inout_asynch() method with a
 * read_attribute_reply() attribute).
 *
 * @subsection AsynReply The AsynReplyNotArrived exception
 * This exception is thrown by the API layer when:
 * @li a request to get asynchronous reply is made and the reply is not yet arrived
 * @li a blocking wait with timeout for asynchronous reply is made and the timeout expired.
 *
 * There is one possible value for the reason field which is API_AsynReplyNotArrived.
 *
 * @subsection EventFailed The EventSystemFailed exception
 * This exception is thrown by the API layer when subscribing or unsubscribing from an event failed. This
 * exception has only one level of Tango::DevError structure. The possible value for the reason field are :
 * @li @b API_NotificationServiceFailed This error occurs when the subscribe_event() method failed trying to access
 * the CORBA notification service
 * @li @b API_EventNotFound This error occurs when you are using an incorrect event_id in the unsubscribe_event()
 * method
 * @li @b API_InvalidArgs This error occurs when nullptrs are passed to the subscribe or unsubscribe event
 * methods
 * @li @b API_MethodArgument This error occurs when trying to subscribe to an event which has already been
 * subscribed to
 * @li @b API_DSFailedRegisteringEvent This error means that the device server to which the device belongs to
 * failed when it tries to register the event. Most likely, it means that there is no event property defined
 * @li @b API_EventNotFound Occurs when using a wrong event identifier in the unsubscribe_event method
 *
 *
 * @subsection NamedDevFailed The NamedDevFailedList exception
 * This exception is only thrown by the DeviceProxy::write_attributes() method. In this case, it is necessary
 * to have a new class of exception to transfer the error stack for several attribute(s) which failed during the
 * writing. Therefore, this exception class contains for each attributes which failed :
 * @li The name of the attribute
 * @li Its index in the vector passed as argument tof the write_attributes() method
 * @li The error stack
 *
 * The following piece of code is an example of how to use this class exception
 * @code
 * catch (Tango::NamedDevFailedList &e)
 * {
 *    long nb_faulty = e.get_faulty_attr_nb();
 *    for (long i = 0;i < nb_faulty;i++)
 *    {
 *       std::cout << "Attribute " << e.err_list[i].name << " failed!" << endl;
 *       for (long j = 0;j < e.err_list[i].err_stack.length();j++)
 *       {
 *          std::cout << "Reason [" << j << "] = " << e.err_list[i].err_stack[j].reason;
 *          std::cout << "Desc [" << j << "] = " << e.err_list[i].err_stack[j].desc;
 *       }
 *    }
 * }
 * @endcode
 * This exception inherits from Tango::DevFailed. It is possible to catch it with a "catch DevFailed" catch
 * block. In this case, like any other DevFailed exception, there is only one error stack. This stack is initialised
 * with the name of all the attributes which failed in its "reason" field.
 *
 * @subsection DevUnlock The DeviceUnlocked exception
 * This exception is thrown by the API layer when a device locked by the process has been unlocked by an
 * admin client. This exception has two levels of Tango::DevError structure. There is only possible value for
 * the reason field which is
 * @li @b API_DeviceUnlocked The device has been unlocked by another client (administration client)
 *
 * The first level is the message reported by the Tango kernel from the server side. The second layer is added
 * by the client API layer with information on which API call generates the exception and device name.
 */

/*******************************************************
 *                                                     *
 *               The Reconnection related page         *
 *                                                     *
 *******************************************************/

/** @page recon Reconnection and exception
 * @section Tango API reconnection
 * The Tango API automatically manages re-connection between client and server in case of communication
 * error during a network access between a client and a server. The transparency reconnection mode allows
 * a user to be (or not be) informed that automatic reconnection took place. If the transparency reconnection
 * mode is not set, when a communication error occurs, an exception is returned to the caller and the connection
 * is internally marked as bad. On the next try to contact the device, the API will try to re-build the
 * network connection. If the transparency reconnection mode is set (the default case), the API will try to re-build the
 network
 * connection has soon as the communication error occurs and the caller is not informed. Several cases are
 * possible. They are summarized in the following table:
 * <TABLE>
 * <TR>
 *    <TH style="text-align:center">Case</TH>
 *    <TH style="text-align:center">Server state</TH>
 *    <TH style="text-align:center">Call nb</TH>
 *    <TH style="text-align:center">Exception (transparency false)</TH>
 *    <TH style="text-align:center">Exception (transparency true)</TH>
 * </TR>
 * <TR>
 *    <TD style="text-align:center" ROWSPAN=4>Server killed and re-started</TD>
 *    <TD style="text-align:center">Server killed before call n</TD>
 *    <TD style="text-align:center">n</TD>
 *    <TD style="text-align:center">CommunicationFailed</TD>
 *    <TD style="text-align:center">ConnectionFailed</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center">Down</TD>
 *    <TD style="text-align:center">n + 1</TD>
 *    <TD style="text-align:center">ConnectionFailed (2 levels)</TD>
 *    <TD style="text-align:center">idem</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center">Down</TD>
 *    <TD style="text-align:center">n + 2</TD>
 *    <TD style="text-align:center">idem</TD>
 *    <TD style="text-align:center">idem</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center">Running</TD>
 *    <TD style="text-align:center">n + x</TD>
 *    <TD style="text-align:center">No exception</TD>
 *    <TD style="text-align:center">No exception</TD>
 * </TR>

 * <TR>
 *    <TD style="text-align:center" ROWSPAN=4>Server died and re-started</TD>
 *    <TD style="text-align:center">Server died before call n</TD>
 *    <TD style="text-align:center">n</TD>
 *    <TD style="text-align:center">CommunicationFailed</TD>
 *    <TD style="text-align:center">ConnectionFailed</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center">Died</TD>
 *    <TD style="text-align:center">n + 1</TD>
 *    <TD style="text-align:center">ConnectionFailed (3 levels)</TD>
 *    <TD style="text-align:center">idem</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center">Died</TD>
 *    <TD style="text-align:center">n + 2</TD>
 *    <TD style="text-align:center">idem</TD>
 *    <TD style="text-align:center">idem</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center">Running</TD>
 *    <TD style="text-align:center">n + x</TD>
 *    <TD style="text-align:center">No exception</TD>
 *    <TD style="text-align:center">No exception</TD>
 * </TR>

 * <TR>
 *    <TD style="text-align:center" ROWSPAN=2>Server killed and re-started</TD>
 *    <TD style="text-align:center">Server killed and re-started before call n</TD>
 *    <TD style="text-align:center">n</TD>
 *    <TD style="text-align:center">CommunicationFailed</TD>
 *    <TD style="text-align:center">No exception</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center">Running</TD>
 *    <TD style="text-align:center">n + x</TD>
 *    <TD style="text-align:center">No exception</TD>
 *    <TD style="text-align:center">No exception</TD>
 * </TR>

 * <TR>
 *    <TD style="text-align:center" ROWSPAN=2>Server died and re-started</TD>
 *    <TD style="text-align:center">Server died and re-started before call n</TD>
 *    <TD style="text-align:center">n</TD>
 *    <TD style="text-align:center">CommunicationFailed</TD>
 *    <TD style="text-align:center">No exception</TD>
 * </TR>
 * <TR>
 *    <TD style="text-align:center">Running</TD>
 *    <TD style="text-align:center">n + x</TD>
 *    <TD style="text-align:center">No exception</TD>
 *    <TD style="text-align:center">No exception</TD>
 * </TR>
 * </TABLE>

 * Please note that the timeout case is managed differently because it will not enter the re-connection
 * system. The transparency reconnection mode is set by default to true starting with Tango version 5.5.
 */

/*******************************************************
 *                                                     *
 *               The telemetry related page            *
 *                                                     *
 *******************************************************/

/** \page telemetry Telemetry Support
 * \include{doc} telemetry.md
 */

/** \page query_event_system Event System Monitoring
 * \include{doc} query_event_system.md
 */

/**
 * \namespace IDL::Tango
 *
 * This is only interesting for cppTango developers.
 *
 * This namespace holds all symbols which are generated by omniidl from the IDL file.
 * The symbols live in the code in the `Tango` namespace as the `IDL::Tango` namespace is madeup.
 */

/**
 * \namespace omniORB4
 *
 * This is only interesting for cppTango developers.
 *
 * This namespace holds all relevant symbols from the omniORB4 library.
 * The symbols live in the code in the their contained namespace as the `omniORB4` namespace is madeup.
 */

#endif /* DOC_DOXYGEN */
