[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (MQTT-394) 3.4 PUBACK – Publish acknowledgement - comments
[ https://issues.oasis-open.org/browse/MQTT-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=64989#comment-64989 ] Ken Borgendale commented on MQTT-394: ------------------------------------- The case that the server does not know whether there is a matching subscriber is generally in the case of complex servers where a message is routed to another server when there might be a matching subscription, not when there is certainly a matching subscription. This could be due to using hashing or an asynchronous removal of subscription routing. > 3.4 PUBACK – Publish acknowledgement - comments > ------------------------------------------------ > > Key: MQTT-394 > URL: https://issues.oasis-open.org/browse/MQTT-394 > Project: OASIS Message Queuing Telemetry Transport (MQTT) TC > Issue Type: Bug > Components: edits > Affects Versions: 5, wd10 > Reporter: Brian Raymor > Assignee: Rahul Gupta > Priority: Trivial > Fix For: 5, wd11 > > > 1. Extra "it": > 1939 Code is specified and 2 if [it] a Return Code is not specified. > 2. Are we correcting figure references at this time or later? It's Figure 3.11. > 1941 The variable header format is illustrated in Figure 3.13 – PUBACK Packet variable header. -- 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]