1
Download User`s Manual - Community RTI Connext Users
Transcript
12.3 Durable Writer History Likewise, the state of a DataReader will be persisted in a database table whose name is generated from the DataReader virtual GUID (see Figure 12.5 History/State Persistence Based on Virtual GUID below). Figure 12.5 History/State Persistence Based on Virtual GUID l l A DataWriter’s virtual GUID can be configured using the member virtual_guid in the DATA_ WRITER_PROTOCOL QosPolicy (DDS Extension) (Section 6.5.3 on page 345). A DataReader’s virtual GUID can be configured using the member virtual_guid in the DATA_ READER_PROTOCOL QosPolicy (DDS Extension) (Section 7.6.1 on page 509). The DDS_PublicationBuiltinTopicData and DDS_SubscriptionBuiltinTopicData structures include the virtual GUID associated with the discovered publication or subscription (see Built-in DataReaders (Section 16.2 on page 772)). 12.3 Durable Writer History The DURABILITY QosPolicy (Section 6.5.7 on page 366) controls whether or not, and how, published samples are stored by the DataWriter application for DataReaders that are found after the samples were initially written. The samples stored by the DataWriter constitute the DataWriter’s history. Connext DDS provides the capability to make the DataWriter history durable, by persisting its content in a relational database. This makes it possible for the history to be restored when the DataWriter restarts. See the Release Notes for the list of supported relational databases. 680
