[OASIS Issue Tracker] (MQTT-257) Flow Control

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

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

Ed Briggs commented on MQTT-257:
--------------------------------

Hi Ken.  The direction to raise it as a new JIRA made in the TC meeting was based on a representation that the JIRA had been closed.  However, when I examined the JIRA earlier, I saw it was not closed, but was still assigned to the editors (marked resolved, but not closed).  Accordingly, the process as I understand it is that updates are to be added to the existing JIRA, which is want I did.   This is because (as I understand it) until it is closed, the editors are still working on it and it is not finished.    I think we may need to clarify the process further.  Cheers, Ed


> Flow Control
> ------------
>
>                 Key: MQTT-257
>                 URL: https://issues.oasis-open.org/browse/MQTT-257
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Bug
>          Components: futures
>    Affects Versions: 5
>            Reporter: Peter Niblett
>            Assignee: Andrew Banks
>             Fix For: 5
>
>
> Developers sometimes ask if there's a way to slow down an MQTT message sender to stop it sending PUBLISH packets faster than the receiver (be it a server or client) is able to process them.
> The receiver can apply back pressure at the TCP/IP level (if it's a TCP/IP transport) or - for QOS 1 and QOS2 - it can delay sending acks so that eventually the sender's inflight message window will fill up, but these mechanisms are a bit crude, and the receiver has no in-band way of letting the sender know what rate is acceptable to it. 
> We need to decide whether this is a problem that affects a significant number of existing or envisaged real-life applications (as opposed to performance and stress tests)



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