Issue 11075: Add Parameter ID for Original Writer Info                                                                                                                                                               (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:
In order to implement the DDS DURABILITY Persistent QoS, a persistence-service needs to send the data that has been received and stored on behalf of the persistent writer.

The service that forwards messages needs to indicate that the forwarded message belongs to the message-stream of another writer, such that if the reader receives the same messages from another source (for example, another forwarding service or the original writer), it can treat them as duplicates.

Resolution:
Introduce a new parameter Id, ORIGINAL_WRITER_INFO, that can appear in parameter lists.

Revised Text:

Add to table 9.4:

Type	PSM Mapping
OriginalWriterInfo_t	struct  {    GUID_t                       originalWriterGUID;    SequenceNumber_t     originalWriterSN;    ParameterList              originalWriterQos;} OriginalWriterInfo;

Append to table 9.13:
Name	ID	Type
PID_ORIGINAL_WRITER_INFO	0x0061	OriginalWriterInfo_t


Add new section:

8.7.6	Original Writer Info

A service supporting the Persistent level of DDS Durability QoS needs to send the data that has been received and stored on behalf of the persistent writer.

This service that forwards messages needs to indicate that the forwarded message belongs to the message-stream of another writer, such that if the reader receives the same messages from another source (for example, another forwarding service or the original writer), it can treat them as duplicates.

The RTPS protocol supports this forwarding of messages by including information of the original writer.  

OriginalWriterInfo_t
attribute	type	value
originalWriterGUID	GUID_t	the GUID of the RTPS Writer that first generated the message
originalWriterSN	SequenceNumber_t	the Sequence Number of the CacheChange as sent from the original writer
originalWriterQos	ParameterList	the list of inline parameters that should apply to the CacheChange as sent by the RTPS Writer that first generated the sample


When a RTPS reader receives this information it will treat it as a normal CacheChange, but once the CacheChange is ready to be commited to the DDS DataReader, it will not commit it.  Instead, it will hand it off to the HistoryCache of the RTPSReader that is communicating with the RTPSWriter indicated in the ORIGINAL_WRITER_INFO inline-Qos and treat it as having the sequence number which appears there and the ParameterList also included in the ORIGINAL_WRITER_INFO.

Resolution: 
Revised Text: 
Actions taken:
May 25, 2007: received issue
May 25, 2007: closed issue
Discussion: 
withdrawn, duplicate of issue 11053
End of Annotations:=====
s is issue # 11075

Add Parameter ID for Original Writer Info

Source:
Real-Time Innovations, Inc. (Ken Brophy, ken@rti.com)
Summary:
In order to implement the DDS DURABILITY Persistent QoS, a persistence-service needs to send the data that has been received and stored on behalf of the persistent writer.

The service that forwards messages needs to indicate that the forwarded message belongs to the message-stream of another writer, such that if the reader receives the same messages from another source (for example, another forwarding service or the original writer), it can treat them as duplicates.

Resolution:
Introduce a new parameter Id, ORIGINAL_WRITER_INFO, that can appear in parameter lists.

Revised Text:

Add to table 9.4:

Type	PSM Mapping
OriginalWriterInfo_t	struct  {    GUID_t                       originalWriterGUID;    SequenceNumber_t     originalWriterSN;    ParameterList              originalWriterQos;} OriginalWriterInfo;

Append to table 9.13:
Name	ID	Type
PID_ORIGINAL_WRITER_INFO	0x0061	OriginalWriterInfo_t


Add new section:

8.7.6	Original Writer Info

A service supporting the Persistent level of DDS Durability QoS needs to send the data that has been received and stored on behalf of the persistent writer.

This service that forwards messages needs to indicate that the forwarded message belongs to the message-stream of another writer, such that if the reader receives the same messages from another source (for example, another forwarding service or the original writer), it can treat them as duplicates.

The RTPS protocol supports this forwarding of messages by including information of the original writer.  

OriginalWriterInfo_t
attribute	type	value
originalWriterGUID	GUID_t	the GUID of the RTPS Writer that first generated the message
originalWriterSN	SequenceNumber_t	the Sequence Number of the CacheChange as sent from the original writer
originalWriterQos	ParameterList	the list of inline parameters that should apply to the CacheChange as sent by the RTPS Writer that first generated the sample


When a RTPS reader receives this information it will treat it as a normal CacheChange, but once the CacheChange is ready to be commited to the DDS DataReader, it will not commit it.  Instead, it will hand it off to the HistoryCache of the RTPSReader that is communicating with the RTPSWriter indicated in the ORIGINAL_WRITER_INFO inline-Qos and treat it as having the sequence number which appears there and the ParameterList also included in the ORIGINAL_WRITER_INFO.