-
Key: C2MS11-251
-
Status: closed
-
Source: Kratos RT Logic, Inc. ( Mr. Mike Anderson)
-
Summary:
In section 8.8.1.3 Mnemonic Value Request Message Contents, there is a kind of odd example paragraph under the explanation of PUBLISH-RATE, that states: "For example, the data provider may know that it is limited to an output rate of 1 megabyte per second. If it is currently near its maximum output rate and after calculating the additional load of the request it would exceed that rate, the data provider may reject the Mnemonic Value Request with a "Failed Completion" status in the RESPONSE-STATUS field, and an optional status of "Unable to meet demand" in the RETURN-VALUE field."
This should probably be placed elsewhere (under a different heading in the same area) and possibly reworded, as an example of not being able to meet the request, instead of an example of PUBLISH-RATE.
The issue is that PUBLISH-RATE is described, then a caveat is given, then an example of the caveat. It winds up confusing as an example of PUBLISH-RATE.
-
Reported: C2MS 1.0 — Thu, 25 Apr 2024 14:11 GMT
-
Disposition: Deferred — C2MS 1.1b1
-
Disposition Summary:
Defer to a later release
Do this later
-
Updated: Mon, 16 Sep 2024 14:18 GMT
C2MS11 — Improve Example Text for Publish Rate
- Key: C2MS11-251
- OMG Task Force: Command and Control Message Specification (C2MS) 1.1 RTF