-
Key: C2MS12-48
-
Status: closed
-
Source: Kratos RT Logic, Inc. ( Mr. Mike Anderson)
-
Summary:
In section 8.9.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: Resolved — C2MS 1.2b1
-
Disposition Summary:
Update Example Text for Publish Rate in 1.2
Remove the discussion of the corner case of not being able to keep up with the request publish rate. It is up to the service provider to decide what to do in that situation; no need to give this one specific detail here.
Additionally there is no need for the PUBLISH-RATE section here. Taking away the detail of the corner case listed above, the only information left in these paragraphs is already described in the preceding table, so just delete the section to be cleaner.
-
Updated: Mon, 30 Mar 2026 14:00 GMT
C2MS12 — Improve Example Text for Publish Rate
- Key: C2MS12-48
- OMG Task Force: Command and Control Message Specification (C2MS) 1.2 RTF