[OASIS Issue Tracker] Commented: (MQTT-19) How Retained publications are deleted.

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

    [ http://tools.oasis-open.org/issues/browse/MQTT-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=33601#action_33601 ] 

Andrew Banks commented on MQTT-19:
----------------------------------

Here are the problems I see in allowing a zero byte retained message to mean deleting an existing retained message.

1) An existing application that uses a zero byte payload message would have to be modified to use MQTT. 
2) We would implicitly give some administrator type privileges (to delete retained publications) to all clients that are permitted to publish on the topic.
3) I am wary of defining more than is necessary about the server processing. In this case, where the server is in fact a connected set of servers it is 
    difficult to guarantee that a retained publication has been deleted because there are many race conditions possible. Such systems can promise very little about
   the order in which actions are taken.

> 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