DDS 1.1 RTF Avatar
  1. OMG Issue

DDS11 — Behavior of DataReaderListener::on_data_available

  • Key: DDS11-91
  • Legacy Issue Number: 8545
  • Status: closed  
  • Source: ADLINK Technology Ltd ( Hans van't Hag)
  • Summary:

    It is not clearly defined whether the on_data_available notification should be generated on every arrival of new data, or just on the status change that happens when coming from a no data situation.
    Resolution:
    For every arrival of new data, a notification should be generated, regardless of whether the previous data has already been read before.
    Revised Text:
    Introduce textual changes to 2.1.4.2.2 that describes the complete set of conditions under which the read-communication status will change. The data available status is considered to have changed each time a new sample becomes available or the ViewState, SampleState, or InstanceState of any existing sample changes for any reason other than a read or take.
    Specific changes that cause the status to be changed include:
    · The arrival of new data
    · The disposal of an instance
    · The loss of liveliness of a writer of an instance when no other writer of that instance exists
    · Unregistration of an instance by the last writer of that instance

  • Reported: DDS 1.0 — Fri, 11 Mar 2005 05:00 GMT
  • Disposition: Resolved — DDS 1.1
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT