It would be useful to have the api/messages response to include the message received time to allow analysis of delivery delays.
A new parameter must be added to the REST API and DAO functions, boolean include_received_at.
Given the standard message format already contains the timestamp, this issue can be addressed by adding a new received_at field to the standard message format. For now this field is added by the DAO in response to this call - no database updates are required.
So the response to these API functions is a list of JSON messages in IoTa internal format. If only timestamps are required, or only timestamps and received at times, the rest of the standard message is dropped.
It would be useful to have the
api/messages
response to include the message received time to allow analysis of delivery delays.A new parameter must be added to the REST API and DAO functions, boolean include_received_at.
Given the standard message format already contains the timestamp, this issue can be addressed by adding a new
received_at
field to the standard message format. For now this field is added by the DAO in response to this call - no database updates are required.So the response to these API functions is a list of JSON messages in IoTa internal format. If only timestamps are required, or only timestamps and received at times, the rest of the standard message is dropped.
only_timestamp = false, include_received_at = false
:only_timestamp = true, include_received_at = true
:only_timestamp = false, include_received_at = true
: