[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (MQTT-546) Improve description of sleeping clients message flows
[ https://issues.oasis-open.org/browse/MQTT-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Johnson updated MQTT-546: ------------------------------- Proposal: Updated the sequence diagram to include device state, message loop, QoS logic, ping-req max receive and ping resp continuation. Resolution: (was: Updated the sequence diagram to include device state, message loop, QoS logic, ping-req max receive and ping resp continuation.) > 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 > Assignee: Simon Johnson > Priority: Minor > Attachments: Sleeping Client Sequence Diagram-2.png > > > 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]