|
| | TDeadline (const dds::core::Duration &d) |
| |
| | TDeadline (const TDeadline &other) |
| |
| | TDeadline () |
| |
| TDeadline & | period (const dds::core::Duration &d) |
| |
| const dds::core::Duration | period () const |
| |
| template<typename ARG > |
| | Value (const ARG &arg) |
| |
| template<typename ARG1 , typename ARG2 > |
| | Value (const ARG1 &arg1, const ARG2 &arg2) |
| |
| template<typename ARG1 , typename ARG2 , typename ARG3 > |
| | Value (const ARG1 &arg1, const ARG2 &arg2, const ARG3 &arg3) |
| |
| template<typename ARG1 , typename ARG2 , typename ARG3 , typename ARG4 > |
| | Value (const ARG1 &arg1, const ARG2 &arg2, const ARG3 &arg3, const ARG4 &arg4) |
| |
| template<typename ARG1 , typename ARG2 , typename ARG3 , typename ARG4 , typename ARG5 > |
| | Value (const ARG1 &arg1, const ARG2 &arg2, const ARG3 &arg3, const ARG4 &arg4, const ARG5 &arg5) |
| |
| template<typename ARG1 , typename ARG2 , typename ARG3 , typename ARG4 , typename ARG5 , typename ARG6 > |
| | Value (const ARG1 &arg1, const ARG2 &arg2, const ARG3 &arg3, const ARG4 &arg4, const ARG5 &arg5, const ARG6 &arg6) |
| |
| | ~Value () |
| |
| const D & | delegate () const |
| |
| D & | delegate () |
| |
| | operator const D & () const |
| |
| | operator D & () |
| |
| bool | operator!= (const Value &other) const |
| |
| const D * | operator-> () const |
| |
| D * | operator-> () |
| |
| Value & | operator= (const Value &other) |
| |
| bool | operator== (const Value &other) const |
| |
template<typename D>
class dds::core::policy::TDeadline< D >
This policy is useful for cases where a Topic is expected to have each instance updated periodically. On the publishing side this setting establishes a contract that the application must meet. On the subscribing side the setting establishes a minimum requirement for the remote publishers that are expected to supply the data values. When the Service matches a DataWriter and a DataReader it checks whether the settings are compatible (i.e., offered deadline period<= requested deadline period) if they are not, the two entities are informed (via the listener or condition mechanism) of the incompatibility of the QoS settings and communication will not occur. Assuming that the reader and writer ends have compatible settings, the fulfillment of this contract is monitored by the Service and the application is informed of any violations by means of the proper listener or condition. The value offered is considered compatible with the value requested if and only if the inequality "offered deadline period <= requested deadline period" evaluates to TRUE. The setting of the DEADLINE policy must be set consistently with that of the TIME_BASED_FILTER. For these two policies to be consistent the settings must be such that "deadline period>= minimum_separation".
Definition at line 329 of file TCorePolicy.hpp.
Public Member Functions inherited from dds::core::Value< D >
1.8.2 
