OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

mqtt message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (MQTT-561) Introduce a broker Timer to monitor sleeping ping flush

     [ https://issues.oasis-open.org/browse/MQTT-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ian Craggs updated MQTT-561:
Section 5.4.19 PINGREQ
(octet 0)|MsgType
ÂÂÂÂ (1)|Max messages (optional)
ÂÂÂÂÂÂÂÂÂ (2)|ClientId (optional)

Table 22: PINGREQ Message
 * Length and MsgType: see section 5.2
 * Max messages: the maximum number of messages that can be received by a client during its awake state. 0 means no limit. This field is optional, included when a sleeping client goes to the awake state, as is the ClientId.

Section 5.4.20 PINGRESP Message

(octet 0)|MsgType
ÂÂÂÂ (1)|Msgs left (optional)
Messages left: the number of messages left when a client is sent back to sleep. Optional - only used at the end of a client awake period. Values can be:
 ** 0 - no messages still queued
 ** 1 through 65534 - the number of messages still queued
 ** 65535 (0xFFFF) - a number of messages are still queued, but not 0 (>=1)


Section 6.14, support of sleeping clients, should be updated to add this behaviour.


> 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
>            Assignee: Ian Craggs
>            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

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]