[ https://issues.oasis-open.org/browse/MQTT-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63082#comment-63082 ]
Jonathan Levell commented on MQTT-257:
--------------------------------------
In the case where the sever elects not to send a QoS=1 message to a client because it has no credit - does the proposal clarify (if so I've missed it) whether the server should continue to send QoS=0 messages (which do not require a credit)? or should sending of all publications (including QoS=0) cease? It seems to me to cease sending all publications including QoS=0 as the client is indicating that it can't keep up.
> 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
>
> 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)
