DDS-XRCE 1.0 FTF Avatar
  1. OMG Issue

DDSXRCE — Read Data Stream

  • Key: DDSXRCE-5
  • Status: closed  
  • Source: eProsima ( Jaime Martin-Losa)
  • Summary:

    In the current specification, the XRCE Clients are not able to select the stream for input data,
    that is, they are not able to tell which stream should be used by the Agents in order to send `DATA` submessages.
    This feature could be very useful for XCRE Clients in order to manage the head-of-line blocking for input messages.

    One possible solution to this issue could be to add a `stream_id` field in the `READ_DATA_Payload`.

    @extensibility(FINAL)
    struct READ_DATA_Payload : BaseObjectRequest {
        ReadSpecification read_specification;
    };
    
    @extensibility(FINAL)
    struct ReadSpecification {
        StreamId    ref_stream;
        DataFormat  data_format;
        @optional string                content_filter_expression;
        @optional DataDeliveryControl   delivery_control;
    };
    
  • Reported: DDS-XRCE 1.0b1 — Wed, 16 Jan 2019 10:37 GMT
  • Disposition: Resolved — DDS-XRCE 1.0
  • Disposition Summary:

    Add a requested stream_id to the ReadSpecification

    Allow the possibility if specifying a requested stream_id inside the ReadSpecification to be used by the Agent when sending the data messages in response.

    Use the mechanism suggested in the issue description.

  • Updated: Tue, 8 Oct 2019 17:54 GMT
  • Attachments: