Issue 11033: Add SerializedDataFragment as Submessage Element                                                                                                                                                        (dds-interop-ftf)
Source: Real-Time Innovations (Mr. Kenneth Brophy, ken@rti.com ken.brophy@rti.com)
Nature: Uncategorized Issue
Severity: 
Summary: Source:
Real-Time Innovations, Inc. (Ken Brophy, ken@rti.com)
Summary:
Encapsulation of serialized data should be the responsibility of the plug-in.  Even though the protocol does not need to interpret the data stream, in the case of fragmented data, the data encapsulation header need only be pre-pended to the first fragment.  Further fragments don't need the encapsulation header.
Resolution:
Add a new SubmessageElement subclass called SerializedDataFragment.

Revised Text:

Renumber 8.3.5.15 (StatusInfo) to 8.3.5.16, and add new section 8.3.5.15

8.3.5.15 SerializedDataFragment

SerializedDataFragment contains the serialized representation of a the value of a data-object that has been fragmented.  Like for unfragmented SerializedData, the RTPS protocol does not interpret the fragmented serialized data-stream.  Therefore, it is represented as opaque data.  For additional information on data encapsulation, see Chapter 10.

Add table 8.32 - Structure of the SerializedDataFragment SubmessageElement
field	type	meaning
value	octet[*]	Serialized data-stream fragment


Replace Figure 8.12 with :

 


Resolution: for updated figure see page 27 of ptc/2007-06-02
Revised Text: Renumber 8.3.5.15 (StatusInfo) to 8.3.5.16, and add new section 8.3.5.15

8.3.5.15 SerializedDataFragment

SerializedDataFragment contains the serialized representation of a the value of a data-object that has been fragmented.  Like for unfragmented SerializedData, the RTPS protocol does not interpret the fragmented serialized data-stream.  Therefore, it is represented as opaque data.  For additional information on data encapsulation, see Chapter 10.

Add table 8.32 - Structure of the SerializedDataFragment SubmessageElement
field	type	meaning
value	octet[*]	Serialized data-stream fragment


Replace Figure 8.12 with :

 


Actions taken:
May 23, 2007: received issue
November 7, 2007: closed issue
Discussion: 
Resolution:
Add a new SubmessageElement subclass called SerializedDataFragment.

End of Annotations:=====
s is issue # 11033   (see attached document)

Add SerializedDataFragment as Submessage Element


Source:
Real-Time Innovations, Inc. (Ken Brophy, ken@rti.com)
Summary:
Encapsulation of serialized data should be the responsibility of the plug-in.  Even though the protocol does not need to interpret the data stream, in the case of fragmented data, the data encapsulation header need only be pre-pended to the first fragment.  Further fragments don't need the encapsulation header.
Resolution:
Add a new SubmessageElement subclass called SerializedDataFragment.

Revised Text:

Renumber 8.3.5.15 (StatusInfo) to 8.3.5.16, and add new section 8.3.5.15

8.3.5.15 SerializedDataFragment

SerializedDataFragment contains the serialized representation of a the value of a data-object that has been fragmented.  Like for unfragmented SerializedData, the RTPS protocol does not interpret the fragmented serialized data-stream.  Therefore, it is represented as opaque data.  For additional information on data encapsulation, see Chapter 10.

Add table 8.32 - Structure of the SerializedDataFragment SubmessageElement
field	type	meaning
value	octet[*]	Serialized data-stream fragment


Replace Figure 8.12 with :