|
TUserData() | TUserData (const dds::core::ByteSeq &seq) |
|
| TUserData (const uint8_t *value_begin, const uint8_t *value_end) |
|
| TUserData (const TUserData &other) |
|
const uint8_t * | begin () const |
|
const uint8_t * | end () const |
|
TUserData & | value (const dds::core::ByteSeq &seq) |
|
template<typename OCTET_ITER > |
TUserData & | value (OCTET_ITER begin, OCTET_ITER end) |
|
const dds::core::ByteSeq | value () 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::TUserData< D >
The purpose of this QoS is to allow the application to attach additional information to the created Entity objects such that when a remote application discovers their existence it can access that information and use it for its own purposes. One possible use of this QoS is to attach security credentials or some other information that can be used by the remote application to authenticate the source. In combination with operations such as ignore_participant, ignore_publication, ignore_subscription, and ignore_topic these QoS can assist an application to define and enforce its own security policies. The use of this QoS is not limited to security, rather it offers a simple, yet flexible extensibility mechanism.
Definition at line 45 of file TCorePolicy.hpp.