Contains the parameters for creating a connext::Replier.
More...
Inherits connext::details::EntityParams.
template<typename TReq, typename TRep>
class connext::ReplierParams< TReq, TRep >
Contains the parameters for creating a connext::Replier.
- See also
- connext::RequesterParams
◆ ReplierParams()
template<typename TReq, typename TRep>
◆ replier_listener()
template<typename TReq, typename TRep>
◆ service_name()
template<typename TReq, typename TRep>
◆ request_topic_name()
template<typename TReq, typename TRep>
Sets a specific request topic name.
The specified topic name will be used, instead of allowing a topic name to be generated based on the service_name. If that topic already exists, it will be reused. This is useful to have the Replier use a DDSContentFilteredTopic to receive only certain requests.
◆ reply_topic_name()
template<typename TReq, typename TRep>
Sets a specific reply topic name.
The specified topic name will be used, instead of allowing a topic name to be generated based on c the service_name. If that topic already exists, it will be reused.
◆ qos_profile()
template<typename TReq, typename TRep>
◆ datawriter_qos()
template<typename TReq, typename TRep>
Sets the quality of service of the reply DataWriter.
- See also
- qos_profile
◆ datareader_qos()
template<typename TReq, typename TRep>
Sets the quality of service of the request DataReader.
- See also
- qos_profile
◆ publisher()
template<typename TReq, typename TRep>
◆ subscriber()
template<typename TReq, typename TRep>
◆ request_type_support()
template<typename TReq, typename TRep>
Sets the type support for the request type.
This parameter is required when TReq
is DDS_DynamicData.
In all other cases, this parameter is ignored and the singleton Reply<TReq, TRep>::RequestTypeSupport is used instead
- See also
- DDSDynamicDataTypeSupport
◆ reply_type_support()
template<typename TReq, typename TRep>
Sets the type support for the reply type.
This parameter is required when TRep
is DDS_DynamicData.
In all other cases, this parameter is ignored and the singleton Reply<TReq, TRep>::RequestTypeSupport is used instead
- See also
- DDSDynamicDataTypeSupport