[OASIS Issue Tracker] (MQTT-504) No way to tell when a retained message was set

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/MQTT-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=67342#comment-67342 ] 

Ken Borgendale commented on MQTT-504:
-------------------------------------

Presumably the issue is that the device does not itself have a clock, or it could just put this information into the payload or a user property.

There are many messaging protocols where the server adds a timestamp to the message..  This is useful for many cases other than retained messages.  

However, in order to get any reasonable amount of interoperability we would need to define a property for this, and also define the format, epoch, and resolution of the timestamp.

> No way to tell when a retained message was set 
> -----------------------------------------------
>
>                 Key: MQTT-504
>                 URL: https://issues.oasis-open.org/browse/MQTT-504
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: New Feature
>          Components: core
>    Affects Versions: 5, CSD01
>            Reporter: Ian Craggs
>            Priority: Minor
>
> I implemented this feature in a broker specific way myself some years back, so I know it's useful.  It was raised on Twitter to me here: https://twitter.com/MichMich/status/903283262415568898
> Maybe expiry would be enough for some use cases.
> We could allow the server to set a property with the received timestamp on the retained message.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)