RTI Connext DDS Micro C API
Version 3.0.2
|
Defines generic classes and macros to support user data types. More...
Data Structures | |
struct | FooTypeSupport |
<<interface>> <<generic>> User data type specific interface. More... |
Macros | |
#define | DDS_DATAWRITER_C(TDataWriter, TData) |
Declares the interface required to support a user data type specific data writer. | |
#define | DDS_TYPESUPPORT_C(TTypeSupport, TData) |
Declares the interface required to support a user data type. | |
#define | DDS_DATAREADER_C(TDataReader, TDataSeq, TData) |
Declares the interface required to support a user data type-specific data reader. |
Typedefs | |
typedef DDS_HANDLE_TYPE_NATIVE | DDS_InstanceHandle_t |
Type definition for an instance handle. |
Functions | |
Foo * | FooTypeSupport_create_data (void) |
<<eXtension>> Create a data type and initialize it. | |
void | FooTypeSupport_delete_data (Foo *sample) |
<<eXtension>> Destroy a user data type instance. | |
DDS_ReturnCode_t | FooTypeSupport_register_type (DDS_DomainParticipant *participant, const char *type_name) |
Allows an application to communicate to RTI Connext DDS Micro the existence of a data type. | |
DDS_ReturnCode_t | FooTypeSupport_unregister_type (DDS_DomainParticipant *participant, const char *type_name) |
Allows an application to unregister a data type from RTI Connext DDS Micro. After calling unregister_type, no further communication using that type is possible. | |
DDS_ReturnCode_t | FooTypeSupport_serialize_data_to_cdr_buffer_ex (char *buffer, unsigned int *length, const TData *a_data, DDS_DataRepresentationId_t representation) |
<<eXtension>> Serializes the input sample into a buffer of octets. | |
DDS_ReturnCode_t | FooTypeSupport_serialize_data_to_cdr_buffer (char *buffer, unsigned int *length, const Foo *a_data) |
<<eXtension>> Serializes the input sample into a CDR buffer of octets. | |
DDS_ReturnCode_t | FooTypeSupport_deserialize_data_from_cdr_buffer (Foo *a_data, const char *buffer, unsigned int length) |
<<eXtension>> Deserializes a sample from a buffer of octets. | |
DDS_Boolean | DDS_InstanceHandle_is_nil (const DDS_InstanceHandle_t *self) |
Compare this handle to DDS_HANDLE_NIL. |
Variables | |
const DDS_InstanceHandle_t | DDS_HANDLE_NIL |
The NIL instance handle. |
Defines generic classes and macros to support user data types.
Defines the DDS user data type support.
DDS specifies strongly typed interfaces to read and write user data. For each data class defined by the application, there is a number of specialised classes that are required to facilitate the type-safe interaction of the application with RTI Connext DDS Micro.
RTI Connext DDS Micro provides an automatic means to generate all these type-specific classes with the RTI IDL Compiler User Manual utility. The complete set of automatic classes created for a hypothetical user data type named Foo
are shown below.
The macros defined here declare the strongly typed APIs needed to support an arbitrary user defined data of type Foo
.
#define DDS_DATAWRITER_C | ( | TDataWriter, | |
TData | |||
) |
Declares the interface required to support a user data type specific data writer.
Foo
Foo
, i.e. FooDataWriter
#define DDS_TYPESUPPORT_C | ( | TTypeSupport, | |
TData | |||
) |
Declares the interface required to support a user data type.
Foo
, i.e. FooTypeSupport
#define DDS_DATAREADER_C | ( | TDataReader, | |
TDataSeq, | |||
TData | |||
) |
Declares the interface required to support a user data type-specific data reader.
Foo
FooSeq sequence of user data type, sequence<Foo>
Foo
, i.e. FooDataReader
typedef DDS_HANDLE_TYPE_NATIVE DDS_InstanceHandle_t |
Type definition for an instance handle.
Handle to identiy different instances of the same DDS_Topic of a certain type.
Foo* FooTypeSupport_create_data | ( | void | ) |
<<eXtension>> Create a data type and initialize it.
The generated implementation of the operation knows how to instantiate a data type and initialize it properly.
All memory for the type is deeply allocated.
void FooTypeSupport_delete_data | ( | Foo * | sample | ) |
<<eXtension>> Destroy a user data type instance.
The generated implementation of the operation knows how to destroy a data type and return all resources.
sample | <<in>> Cannot be NULL. |
DDS_ReturnCode_t FooTypeSupport_register_type | ( | DDS_DomainParticipant * | participant, |
const char * | type_name | ||
) |
Allows an application to communicate to RTI Connext DDS Micro the existence of a data type.
The generated implementation of the operation embeds all the knowledge that has to be communicated to the middleware in order to make it able to manage the contents of data of that type. This includes in particular the key definition that will allow RTI Connext DDS Micro to distinguish different instances of the same type.
The same ::DDS_TypeSupport can be registered multiple times with a DDS_DomainParticipant using the same or different values for the type_name
. If register_type
is called multiple times on the same ::DDS_TypeSupport with the same DDS_DomainParticipant and type_name
, the second (and subsequent) registrations are ignored by the operation fails with DDS_RETCODE_OK.
type_name
to register two different ::DDS_TypeSupport with the same DDS_DomainParticipant, or else the operation will fail and DDS_RETCODE_PRECONDITION_NOT_MET will be returned. participant | <<in>> the DDS_DomainParticipant to register the data type Foo with. Cannot be NULL. |
type_name | <<in>> the type name under with the data type Foo is registered with the participant; this type name is used when creating a new DDS_Topic. (See DDS_DomainParticipant_create_topic.) The name may not be NULL or longer than 255 characters. |
DDS_ReturnCode_t FooTypeSupport_unregister_type | ( | DDS_DomainParticipant * | participant, |
const char * | type_name | ||
) |
Allows an application to unregister a data type from RTI Connext DDS Micro. After calling unregister_type, no further communication using that type is possible.
The generated implementation of the operation removes all the information about a type from RTI Connext DDS Micro. No further communication using that type is possible.
type_name
is registered with the participant and all DDS_Topic objects referencing the type have been destroyed. If the type is not registered with the participant, or if any DDS_Topic is associated with the type, the operation will fail with DDS_RETCODE_ERROR. participant | <<in>> the DDS_DomainParticipant to unregister the data type Foo from. Cannot be NULL. |
type_name | <<in>> the type name under with the data type Foo is registered with the participant. The name should match a name that has been previously used to register a type with the participant. Cannot be NULL. |
DDS_ReturnCode_t FooTypeSupport_serialize_data_to_cdr_buffer_ex | ( | char * | buffer, |
unsigned int * | length, | ||
const TData * | a_data, | ||
DDS_DataRepresentationId_t | representation | ||
) |
<<eXtension>> Serializes the input sample into a buffer of octets.
This function serializes a sample into a buffer of octets using the input data representation. See FooTypeSupport_serialize_data_to_cdr_buffer for details.
a_data | <<in>>. Input sample. Cannot be NULL. |
buffer | <<out>>. Serialization buffer. |
length | <<inout>>. Serialization buffer length. |
representation | <<in>>. Representation used to serialize the data. |
DDS_ReturnCode_t FooTypeSupport_serialize_data_to_cdr_buffer | ( | char * | buffer, |
unsigned int * | length, | ||
const Foo * | a_data | ||
) |
<<eXtension>> Serializes the input sample into a CDR buffer of octets.
This function serializes a sample into a buffer of octets and it uses CDR as the data representation. Calling this function is equivalent to calling FooTypeSupport_serialize_data_to_cdr_buffer_ex with ::DDS_AUTO_DATA_REPRESENTATION as the representation.
The input buffer must be big enough to store the serialized representation of the sample. Otherwise, the function will return an error.
To determine the minimum size of the input buffer, the user must call this method with the buffer set to NULL.
a_data | <<in>>. Input sample. Cannot be NULL. |
buffer | <<out>>. Serialization buffer. |
length | <<inout>>. When buffer is set to NULL, after the function executes, length will contain a buffer size big enough to hold the serialized data. When buffer is not NULL, length must contain the size of the input buffer when the function is invoked. After the function executes, length will be updated to contain the actual size of the serialized content, which may be smaller than the size obtained when buffer is set to NULL. |
DDS_ReturnCode_t FooTypeSupport_deserialize_data_from_cdr_buffer | ( | Foo * | a_data, |
const char * | buffer, | ||
unsigned int | length | ||
) |
<<eXtension>> Deserializes a sample from a buffer of octets.
This function deserializes a sample from a CDR buffer of octets.
The content of the buffer generated by the function FooTypeSupport_serialize_data_to_cdr_buffer can be provided to this function to get the sample back.
sample | <<in>>. Output sample. Cannot be NULL. |
buffer | <<in>>. Deserialization buffer. Cannot be NULL. |
length | <<in>>. Length of the serialized representation of the sample in the buffer. |
DDS_Boolean DDS_InstanceHandle_is_nil | ( | const DDS_InstanceHandle_t * | self | ) |
Compare this handle to DDS_HANDLE_NIL.
const DDS_InstanceHandle_t DDS_HANDLE_NIL |