[OASIS Issue Tracker] (MQTT-358) Receive Maximum - Not setting the Receive Maximum value

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/MQTT-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=64788#comment-64788 ] 

Brian Raymor commented on MQTT-358:
-----------------------------------

This is two sentences. Change 1351 to "the Client. It does not ..."

1350 The Server uses this value to limit the number of publications that it is willing to process concurrently for
1351 the Client, it does not provide a mechanism to limit the QoS 0 publications that the Client might try to
1352 send.

> Receive Maximum - Not setting the Receive Maximum value 
> --------------------------------------------------------
>
>                 Key: MQTT-358
>                 URL: https://issues.oasis-open.org/browse/MQTT-358
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Bug
>          Components: edits
>    Affects Versions: 5, wd10
>            Reporter: Brian Raymor
>            Assignee: Rahul Gupta
>            Priority: Minor
>             Fix For: 5, wd10
>
>
> I'm not sure why this text below is separated out in a comment. It seems important to document the "default" value of Receive Maximum.
> 1083 Non normative comment
> 1084 Not setting the Receive Maximum value has the same effect as setting it to 65535.
> It's also awkwardly phrased. Why not include a reference in the main text:
> If Receive Maximum is absent, then its value defaults to 65535.



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