Next in thread → Next in month →

[OASIS Issue Tracker] (MQTT-404) Question - Reason String - representing the reason for the *connection* failure

From
OASIS Issues Tracker <>
Date
2017-01-19T23:16:11+00:00
ID
Thread
[OASIS Issue Tracker] (MQTT-404) Question - Reason String - representing the reason for the *connection* failure
[ https://issues.oasis-open.org/browse/MQTT-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=64980#comment-64980 ] 

Brian Raymor commented on MQTT-404:
-----------------------------------

I apologize for the lack of clarity. My aim was to point out that the Reason String can be returned in many different contexts - for example, PUBREC or PUBREL. Does "connection failure" express the purpose for all cases -or- is it an artifact on cutting-n-pasting?

> Question - Reason String - representing the reason for the *connection* failure 
> --------------------------------------------------------------------------------
>
>                 Key: MQTT-404
>                 URL: https://issues.oasis-open.org/browse/MQTT-404
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Bug
>          Components: edits
>    Affects Versions: 5, wd10
>            Reporter: Brian Raymor
>            Assignee: Ed Briggs
>            Priority: Minor
>             Fix For: 5, wd11
>
>
> While it makes sense for CONNACK, is "connection failure" the appropriate description for all cases? Perhaps "operation failure" or "failure"? 
> 1476 31 (0x1F) Byte Identifier of the Reason String. Followed by the UTF-8 encoded string representing the
> 1477 reason for the *connection* failure. 



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
Next in thread → Next in month →