3.4. Subscriber

A subscription is defined by the association of a DataReader to a Subscriber. To start receiving updates of a publication, the application creates a new DataReader in a Subscriber. This DataReader will be bound to the Topic that describes the data type that is going to be received. The DataReader will then start receiving data value updates from remote publications that match this Topic.

When the Subscriber receives data, it informs the application that new data is available. Then, the application can use the DataReader to get the received data.

Subscriber class diagram

• 3.4.1. Subscriber
  • 3.4.1.1. SubscriberQos
    • 3.4.1.1.1. Default SubscriberQos
• 3.4.2. SubscriberListener
• 3.4.3. Creating a Subscriber
  • 3.4.3.1. Profile based creation of a Subscriber
  • 3.4.3.2. Deleting a Subscriber
• 3.4.4. DataReader
  • 3.4.4.1. DataReaderQos
    • 3.4.4.1.1. Default DataReaderQos
• 3.4.5. DataReaderListener
• 3.4.6. Creating a DataReader
  • 3.4.6.1. Profile based creation of a DataReader
  • 3.4.6.2. Creating a DataWriter with a custom PayloadPool
  • 3.4.6.3. Deleting a DataReader
• 3.4.7. SampleInfo
  • 3.4.7.1. sample_state
  • 3.4.7.2. view_state
  • 3.4.7.3. instance_state
  • 3.4.7.4. disposed_generation_count
  • 3.4.7.5. no_writers_generation_count
  • 3.4.7.6. sample_rank
  • 3.4.7.7. generation_rank
  • 3.4.7.8. absolute_generation_rank
  • 3.4.7.9. source_timestamp
  • 3.4.7.10. instance_handle
  • 3.4.7.11. publication_handle
  • 3.4.7.12. valid_data
  • 3.4.7.13. sample_identity
  • 3.4.7.14. related_sample_identity
• 3.4.8. Accessing received data
  • 3.4.8.1. Loaning and Returning Data and SampleInfo Sequences
  • 3.4.8.2. Processing returned data
  • 3.4.8.3. Accessing data on callbacks
  • 3.4.8.4. Accessing data with a waiting thread
    • 3.4.8.4.1. Wait-sets and DataAvailable status condition
    • 3.4.8.4.2. DataReader non-blocking calls