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

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

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

Raphael Cohen commented on MQTT-79:
-----------------------------------

The key points were:-

1 Clarify what store means and the fact that the server may purge / remove stuff as it sees fit.
2 An administrator may purge storage at any time
3 Elaborate minimal storage commitment for each QoS ?
4 QoS 0 messages may disappear at any time
5 Storage with respect to system outages / failures ?

Proposal above covers 2, 3 and 4 and second-half of 1.

First-half of 1 is covered when we describe store elsewhere IIRC.

5 is tricky to define...

> 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