-
Key: OARIS21-7
-
Status: closed
-
Source: BAE Systems ( Jia Liu)
-
Summary:
The following is the description of request_id in oaris 2.0 spec:
7.3.12.6 request_id_type
Type: IDLTypeDef unsigned long long
Package: Requests
The purpose of the request_id is to uniquely relate responses of the subsystem (server) to requests of the CMS (client). The request_id is set by the client. It is the responsibility of the client to specify a system-wide unique request_id (e.g. based on a combination of client id and a sequence number / time of request). Here it indicates that CMS as client should specify request_id. But in section 7.7.5.3 Provide_Subsystem_Identification, it documents that it should be the subsystem to initiate the communication to CMS, which implies subsystem will need to specify request_id required in receive_sub_identification_data_type before sending it to CMS. -
Reported: OARIS 2.0b1 — Tue, 13 Sep 2022 16:29 GMT
-
Disposition: Deferred — $issue.fixedSpecification.name
-
Disposition Summary:
This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force
-
Updated: Tue, 9 Jul 2024 14:40 GMT
OARIS21 — contradiction on who (subsystem or CMS) should initiate the identification process and set the request id.
- Key: OARIS21-7
- OMG Task Force: Open Architecture Radar Interface Standard (OARIS) 2.1 RTF