![]() |
CoreDX Data Distribution Service
The High Performance, Small Footprint DDS from Twin Oaks Computing, Inc
|
The DDS_DataWriter entity provides an interface for the application to publish (write) data. More...
The DDS_DataWriter entity provides an interface for the application to publish (write) data.
The DataWriter is an abstract 'class' that is extended to support a particular data type required by the application. A DataReader is associated with, and writes on, a single Topic.
|
related |
This operation manually asserts the liveliness of the DataWriter dw.
This operation is useful if the LIVELINESS QoS setting is MANUAL_BY_PARTICIPANT or MANUAL_BY_TOPIC; otherwise, it has no effect.
|
related |
Indicates that the instance no longer exists.
If handle is not HANDLE_NIL, then handle must identify a valid instance that has been previously registered or written by this DataWriter. The current time is used as the timstamp.
|
related |
Indicates that the instance no longer exists.
If handle is not HANDLE_NIL, then handle must identify a valid instance that has been previously registered or written by this DataWriter. The source_timestamp is used as the source timstamp for the published message.
|
related |
Enables the DDS_DataWriter.
A DataWriter is created either enabled or not based on the DDS_PublisherQos setting entity_factory. When a DataWriter is not enabled, only the following sub-set of all DataWriter operations are legal:
Any other operation may return the DDS_NOT_ENABLED error. DDS_DataWriter_enable() may be called on an already enabled DataWriter [it will have no effect].
|
related |
Provides access to the current cache statistics of the DataWriter.
This routine will populate 'stats' with the current statistics.
|
related |
This routine will populate the data structure indicated by key_holder with the key infomation identified by handle.
|
related |
This operation returns the currently installed DDS_DataWriterListener.
|
related |
This operation returns the currently installed DDS_DataWriterListener_cd.
|
related |
Provides access to the current DDS_LivelinessLostStatus of the DataWriter.
As a side-effect, this routine will reset the total_count_change status field to zero.
|
related |
This operation returns data that describes a particular matched DataReader identified by subscription_handle.
An appropriate handle can be obtained through a call to DDS_DataWriter_get_matched_subscriptions().
If subscription_handle does not identify a matched DataReader, this routine will return DDS_RETCODE_PRECONDITION_NOT_MET. To reclaim any memory returned in the 'subscription_data' parameter, call DDS_DCPSSubscription_clear(subscription_data).
|
related |
This operation retrieves the list of DataReaders currently matched with the DataWriter dw.
This list will include the handles that identify DataReaders which have matching Topic and compatible QoS with DataWriter.
If a DataReader has been ignored by a call to DDS_DomainParticipant_ignore_subscription(), then it will not appear in the list.
|
related |
Provides access to the current DDS_OfferedDeadlineMissedStatus of the DataWriter.
As a side-effect, this routine will reset the total_count_change status field to zero.
|
related |
Provides access to the current DDS_OfferedIncompatibleQosStatus of the DataWriter.
As a side-effect, this routine will reset the total_count_change status field to zero.
|
related |
Provides access to the current DDS_PublicationMatchedStatus of the DataWriter.
As a side-effect, this routine will reset the total_count_change and current_count_change status fields to zero.
|
related |
Returns the current DDS_DataWriterQos settings held in the DataWriter dw.
This routines copies data from the DataWriter QoS properties into qos.
|
related |
This returns the list of triggered communication statuses in the DataWriter.
If the DataWriter is not enabled, all statuses will be untriggered.
|
related |
This operation allows access to the DDS_StatusCondition associated with the DataWriter.
The returned condition can be added to a DDS_WaitSet.
|
related |
Returns the handle that identifies the data instance provided in instance_data.
The 'key' field values of the data are associated with a unique handle.
|
related |
Declares the existance of an instance identified by the 'key fields' in instance_data.
The handle that uniquely identifies the instance is returned. The current time is used as the timestamp.
|
related |
Declares the existance of an instance identified by the 'key fields' in instance_data.
The handle that uniquely identifies the instance is returned. The source_timestamp is used as the timestamp.
|
related |
Installs a DDS_DataWriterListener on DataWriter dw.
Only one listener may be attached to a DataWriter at a time. A call to set_listener() will replace any current listener with a_listener.
a_listener can be NULL, which indicates a listener that does nothing.
The infrastructure will make an internal copy of the listener structure so that it need not be persisted by the application.
|
related |
Installs a DDS_DataWriterListener_cd on DataWriter dw.
Only one listener may be attached to a DataWriter at a time. A call to set_listener_cd() will replace any current listener with a_listener.
a_listener can be NULL, which indicates a listener that does nothing.
The infrastructure will hold a pointer to the listener structure which means that it must be persisted by the application.
|
related |
Sets the DDS_DataWriterQos values.
These QoS values affect the behavior of the DDS_DataWriter.
|
related |
Indicates that the writer will no longer be providing updates the specified instance.
If handle is not HANDLE_NIL, then handle must identify a valid instance that has been previously registered or written by this DataWriter. The current time is used as the timstamp.
|
related |
Indicates that the writer will no longer be providing updates the specified instance.
If handle is not HANDLE_NIL, then handle must identify a valid instance that has been previously registered or written by this DataWriter. The provided source_timestamp is used as the timstamp.
|
related |
Block until this writer has received acknowledgements for all written data.
This routine will block until all data written by the writer has been acknowledged, or until the 'max_wait' duration has passed. 'max_wait' can be set to INFINITE, in which case this routine may block indefinitely.
DDS_RETCODE_TIME_OUT | if 'max_wait' passes before all acks are received |
DDS_RETCODE_OK | if all acks have been received before 'max_wait' |
DDS_RETCODE_PRECONDITION_NOT_MET | if QoS.rtps_writer.require_acks = 0 |
|
related |
Publishes the provided instance_data.
If handle is HANDLE_NIL, then the handle is determined from the 'key fields' of instance_data. The current time is used as the source timestamp for the published data. This routine may block if RELIABILITY kind == RELIABLE, RESOURCE_LIMITS are not UNLIMITED, and the local resources are exhausted. The routine will block at most 'max_blocking_time' as configured in the RELIABLITY QoS. If the routine is still unable to handle the data, after blocking, then DDS_RETCODE_TIMEOUT is returned.
The routine may return DDS_RETCODE_OUT_OF_RESOURCES if it is determined that no amount of blocking will allow the data to be processed.
On success, DDS_RETCODE_OK is returned.
|
related |
Publishes the provided instance_data.
If handle is HANDLE_NIL, then the handle is determined from the 'key fields' of instance_data. The source_timestamp is used as the source timestamp for the published data. This routine may block if RELIABILITY kind == RELIABLE, RESOURCE_LIMITS are not UNLIMITED, and the local resources are exhausted. The routine will block at most 'max_blocking_time' as configured in the RELIABLITY QoS. If the routine is still unable to handle the data, after blocking, then DDS_RETCODE_TIMEOUT is returned.
The routine may return DDS_RETCODE_OUT_OF_RESOURCES if it is determined that no amount of blocking will allow the data to be processed.
On success, DDS_RETCODE_OK is returned.