-
Key: DSS2-97
-
Legacy Issue Number: 5206
-
Status: closed
-
Source: MITRE ( Ms. Susan Symington)
-
Summary:
Table 17: interaction subclass HLAmanager.HLAfederate.HLAreport.HLAreportReflectionsReceived: how defined. As currently worded, the text is not clear as to whether the number of reflections received is defined as the number of times the Reflect Attribute Values service was invoked at the federate for all object instances of a given object class, or the number of instance attribute value reflections by the federate for all object instances of a given object class.
It is recommended that text be added to clarify that the number of reflections is defined as the number of instance attribute value reflections. That is, if a federate has received the Reflect Attribute Values service invocation twice, and in one of these service invocations were arguments for an object instance of class A and n instance attributes of type reliable, and in another of these service invocations were arguments for an object instance of class A and m instance attributes of type best-effort, then in response to an interaction of class Manager.Federate.Request.RequestReflectionsReceived, two Manager.Federate.Report.ReportReflectionsReceived interactions should be sent: one for transportation type reliable with a reflect count of n for object class A, and one for transportation type best-effort with a reflection count of m for object class A. Furthermore, if that federate receives an additional Reflect Attribute Values service invocation for an object instance of class A that contains a single attribute/value pair as argument, and the attribute is a reliable attribute that had also had a value reflected previously, then in response to an interaction of class Manager.Federate.Request.RequestReflectionsReceived, two Manager.Federate.Report.ReportReflectionsReceived interactions should be sent: one for transportation type reliable with a reflect count of n + 1 for object class A, and one for transportation type best-effort with a reflection count of m for object class A
-
Reported: DSS 1.1 — Wed, 10 Apr 2002 04:00 GMT
-
Disposition: Resolved — DSS 2.0
-
Disposition Summary:
Add the suggested clarifying text.
-
Updated: Fri, 6 Mar 2015 20:58 GMT
DSS2 — Table 17: interaction subclass, another issue
- Key: DSS2-97
- OMG Task Force: Distributed Simulation V2.0 FTF