https://guides.github.com/features/mastering-markdown/In order for the ui to support status, the volttron central api responses should include a status field for all api responses. A status response will be contained in the normal json rpc protocol format.
# There will be an optional status object that can be appended onto the json rpc
# response as follows.
{
"result": {
"data_result_of_call": [ "data", "data", "data2"],
"status": {
"code": "success or errror",
"msg": "This is the message to be displayed as a result."
}
}
}
Things that must contain statuses
[x] Registering a platform through volttron central
[ ] Announcing a platform is available to be managed (registration from the platform side)
[ ] The calling of a function on a particular agent (not whether the function executed successfully, but that it was attempted).
As an integration point. The platform queries the platform historian for a specific topic. While this does fall into the third bullet above, this is an instance where the platform historian has knowledge of whether a topic exists or not. The platform historian agent can raise an exception that gets propogated up to the platform and either th platform itself or the vc can translate that into the proper response.
https://guides.github.com/features/mastering-markdown/In order for the ui to support status, the volttron central api responses should include a status field for all api responses. A status response will be contained in the normal json rpc protocol format.
Things that must contain statuses
As an integration point. The platform queries the platform historian for a specific topic. While this does fall into the third bullet above, this is an instance where the platform historian has knowledge of whether a topic exists or not. The platform historian agent can raise an exception that gets propogated up to the platform and either th platform itself or the vc can translate that into the proper response.