Issue 10740: DLRL object (data-distribution-rtf)
Source: PrismTech (Mr. Erik Hendriks, erik.hendriks(at)prismtech.com)
Nature: Revision
Severity: 
Summary: Problem:

What should happen to an object that passes a contentfilter once, but then its update gets blocked by the contentfilter? Currently the DLRL behaves as if no update was received, potentially resulting in the wrong assumption that the previous state is still the most recent state available.

Solution:

This problem cannot be solved without some support on DCPS ContentFilteredTopic level as well, since a special state needs to be introduced to represent instances that are blocked by a filter. The idea is to introduce a special state called NOT_COMPLIANT, that has similar properties to the DELETED state, except for the fact that it has another meaning. This NOT_COMPLIANT state can also be used for other purposes (See issue PT-DLRL-ARCH-0029).

TBD.

Resolution: 
Revised Text: 
Actions taken:
February 14, 2007: received issue
Discussion: 
Indicate what should happen to a DLRL object that passed a ContentFilter before, but then later on gets blocked by this filter.
End of Annotations:=====
s is issue # 10740	From: "Erik Hendriks" <Erik.Hendriks@prismtech.com>


DLRL object
Indicate what should happen to a DLRL object that passed a ContentFilter before, but then later on gets blocked by this filter.

Problem:

What should happen to an object that passes a contentfilter once, but then its update gets blocked by the contentfilter? Currently the DLRL behaves as if no update was received, potentially resulting in the wrong assumption that the previous state is still the most recent state available.

Solution:

This problem cannot be solved without some support on DCPS ContentFilteredTopic level as well, since a special state needs to be introduced to represent instances that are blocked by a filter. The idea is to introduce a special state called NOT_COMPLIANT, that has similar properties to the DELETED state, except for the fact that it has another meaning. This NOT_COMPLIANT state can also be used for other purposes (See issue PT-DLRL-ARCH-0029).

TBD.