[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (MQTT-19) How Retained publications are deleted.
[ http://tools.oasis-open.org/issues/browse/MQTT-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=33580#action_33580 ] Dominik Obermaier commented on MQTT-19: --------------------------------------- I think this behaviour should not be optional but instead it should be mandatory. This is the only chance for a client to delete a retained message. When this behaviour would be removed from the specification, it is impossible to implement a scenario where a "last good message" could be deleted by clients. Afaik most brokers implement the behaviour of deleting a retained publish when sending a zero byte payload message with the retained flag set and there are probably several projects out there which rely on this feature. > How Retained publications are deleted. > -------------------------------------- > > Key: MQTT-19 > URL: http://tools.oasis-open.org/issues/browse/MQTT-19 > Project: OASIS Message Queuing Telemetry Transport (MQTT) TC > Issue Type: Improvement > Components: core > Reporter: Andrew Banks > > There specification suggests that a retained message published with a zero byte payload can be used to cause a retained message to be deleted by the server, although it > leaves this behavior as optional. It is not clear whether the zero length message should be sent to subscribers. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]