Issue 10743: instance_state of a DCPS instance becomes NOT_ALIVE_NO_WRITERS (data-distribution-rtf)
Source: PrismTech (Mr. Erik Hendriks, erik.hendriks(at)prismtech.com)
Nature: Revision
Severity: 
Summary: Problem:

It should clearly be stated what to do to the lifecycle of a DLRL object when the instance_state of the corresponding DCPS instance becomes NOT_ALIVE_NO_WRITERS.

Solution:

Our proposal is to mark this situation in the DLRL object, but not to start a new DLRL generation. There must be some mechanism however to notify the application about changes to the Liveliness of such an object. We propose to add a specific ObjectState called LIVELINESS_LOST, which is a separate state variable from the ObjectState. A transition to this state can be signalled by a callback method on the ObjectListener called "on_object_liveliness_lost". When liveliness is regained, the ObjectState can revert back to the LIVELINESS_ASSURED. A new callback should be added for that situation called "on_object_liveliness_regained". Similarly the ObjectHome should provide methods called "get_liveliness_lost_objects" and "get_liveliness_regained_objects".

TBD.

Resolution: 
Revised Text: .
Actions taken:
February 14, 2007: received issue
Discussion: 
Indicate what to do when the instance_state of a DCPS instance becomes NOT_ALIVE_NO_WRITERS.
End of Annotations:=====
s is issue # 10743	From: "Erik Hendriks" <Erik.Hendriks@prismtech.com>


instance_state of a DCPS instance becomes NOT_ALIVE_NO_WRITERS
Indicate what to do when the instance_state of a DCPS instance becomes NOT_ALIVE_NO_WRITERS.

Problem:

It should clearly be stated what to do to the lifecycle of a DLRL object when the instance_state of the corresponding DCPS instance becomes NOT_ALIVE_NO_WRITERS.

Solution:

Our proposal is to mark this situation in the DLRL object, but not to start a new DLRL generation. There must be some mechanism however to notify the application about changes to the Liveliness of such an object. We propose to add a specific ObjectState called LIVELINESS_LOST, which is a separate state variable from the ObjectState. A transition to this state can be signalled by a callback method on the ObjectListener called "on_object_liveliness_lost". When liveliness is regained, the ObjectState can revert back to the LIVELINESS_ASSURED. A new callback should be added for that situation called "on_object_liveliness_regained". Similarly the ObjectHome should provide methods called "get_liveliness_lost_objects" and "get_liveliness_regained_objects".

TBD.