mqtt message

Subject: [OASIS Issue Tracker] (MQTT-546) Improve description of sleeping clients message flows

From: OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>
To: mqtt@lists.oasis-open.org
Date: Tue, 28 Apr 2020 13:25:00 +0000 (UTC)

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

Simon Johnson commented on MQTT-546:
------------------------------------

I had assumed that the PUBLISH part of the sequence diagram was short hand for the FULL publish interaction, regardless of QoS and I would expect consistency across all QoS, that is a PINGRESP to only be issued by the broker upon successful acknowledgments of all messages.

> Improve description of sleeping clients message flows
> -----------------------------------------------------
>
>                 Key: MQTT-546
>                 URL: https://issues.oasis-open.org/browse/MQTT-546
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: MQTT-SN
>    Affects Versions: MQTT-SN-1.2
>            Reporter: Ian Craggs
>            Priority: Minor
>
> From an old set of comments about possible improvements for version '1.3'.
> When a client awakens by sending a PINGREQ, the server responds by sending queued up messages before sending the PINGRESP.Â If queued-up messages are of QoS 1 or 2, the PINGRESP is sent after the entire message exchanges are completed, that is, on receipt of all PUBACKs or PUBCOMPs.



--
This message was sent by Atlassian Jira
(v8.3.3#803004)