-
Key: DSS2-17
-
Legacy Issue Number: 5125
-
Status: closed
-
Source: MITRE ( Ms. Susan Symington)
-
Summary:
It should be noted in conjunction with this service that the standard is silent regarding what will happen in the case in which a federate attempts to take ownership of an instance attribute of an object instance for which another federate has already scheduled a timed deletion. That is, if a federate schedules the deletion of an object instance for a time in the future, that object instance may still be discovered by other federates, and updates to instance attributes of that object instance may still be received by other federates, until their logical times are greater than or equal to the specified time of the deletion. If those other federates are allowed to take ownership of any of the instance attributes owned by the federate that scheduled the delete, then it would be possible for strange things to occur within the federation execution, such as a federate that owns the HLAprivilegeToDelete instance attribute of an object instance receiving a Remove Object Instance callback for that object instance. The standard does not specify the RTI's behavior in such circumstances.
-
Reported: DSS 1.1 — Tue, 9 Apr 2002 04:00 GMT
-
Disposition: Resolved — DSS 2.0
-
Disposition Summary:
Add text that addresses this issue.
-
Updated: Fri, 6 Mar 2015 20:58 GMT
DSS2 — Service 6.10: Delete Object Instance
- Key: DSS2-17
- OMG Task Force: Distributed Simulation V2.0 FTF