[ https://issues.oasis-open.org/browse/MQTT-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=76865#comment-76865 ]
Ian Craggs commented on MQTT-561:
---------------------------------
We discussed alternatives to a timer:
* having a field on the pingreq which indicates how many messages can be processed by the client in one awakening
* having a field on the pingresp which indicates how many messages are still queued (could be 0, an 'accurate' number, or FFFF - 'more than 0')
> Introduce a broker Timer to monitor sleeping ping flush
> -------------------------------------------------------
>
> Key: MQTT-561
> URL: https://issues.oasis-open.org/browse/MQTT-561
> Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
> Issue Type: Improvement
> Components: MQTT-SN
> Affects Versions: MQTT-SN-1.2
> Reporter: Simon Johnson
> Priority: Major
>
> We should consider advising or mandating a broker monitored timer across the flush operation of a sleeping PING. In reality a sleeping client may have many messages to receive, which when sent on slow transport layers leads to devices being awake far longer than they may wish.
--
This message was sent by Atlassian Jira
(v8.3.3#803004)
