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-464) Add reason code 150 to PUBACK packet


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

Brian Raymor updated MQTT-464:
------------------------------

    Component/s: core

> Add reason code 150 to PUBACK packet
> ------------------------------------
>
>                 Key: MQTT-464
>                 URL: https://issues.oasis-open.org/browse/MQTT-464
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 5, wd14
>            Reporter: Konstantin Dotchkoff
>             Fix For: 5, wd14
>
>
> Line 2111: Table 3-5 - PUBACK Reason Codes
> need to add code value 150 (0x96) "Message rate too high" to the table.
> Line 881: Table 2-4 Reason Codes
> add PUBACK in the Packets column for Value 150 (0x96) "Message rate too high" 
> This code is different than return code 151 and needed for PUBACK, to inform the Sender that it has temporarily exceeded the throughput limit (vs. the cumulative (daily/monthly) quota for a customer, represented by value 151).
> Example: Sender can wait for a period of time and then continue sending messages, instead of forcing it to disconnect and perform a resource intense reconnect.
> This issue was originally reported in MQTT-417, which doesn't seem to be applied in WD14. 



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)


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