[OASIS Issue Tracker] Commented: (MQTT-79) Allow deletion of QoS1/2 messages in rare circumstances

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

Peter Niblett commented on MQTT-79:
-----------------------------------

Title should be broadened so that the subject of the issue includes QoS 0.  Also the circustances in which QoS 0 get deleted might not be that rare

> Allow deletion of QoS1/2 messages in rare circumstances
> -------------------------------------------------------
>
>                 Key: MQTT-79
>                 URL: http://tools.oasis-open.org/issues/browse/MQTT-79
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 3.1.1
>            Reporter: Raphael Cohen
>             Fix For: 3.1.1
>
>
> (Reference MQTT-7).
> After " the client and server MUST store qos 1 and qos 2 messages, including those new messages due to active subscriptions on the server ", insert:-
> The server MAY then delete such messages at any time if required to do so because of resource constraints, administrative action or becoming aware of external knowledge that the message can no longer be delivered to any current or future client.

-- 
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