You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2018/11/25 17:06:40 UTC
[GitHub] cbornet opened a new issue #3052: WebSocket manual consumer flow
control
cbornet opened a new issue #3052: WebSocket manual consumer flow control
URL: https://github.com/apache/pulsar/issues/3052
Currently in the WebSocket proxy, `receiverQueueSize` is used for both sizing the internal buffer of incoming messages and also to ensure flow control with the WS-proxy client by stopping sending messages if the number of unacked messages reaches the `receiverQueueSize`.
This is a simple mode but there are cases where you want to have more control over how the messages are delivered and acked. For instance you may want to ack the messages in a distinct connection. Or you may want to get a certain amount of messages in a "poll" fashion. Also the pull-mode is generally the best way to provide back-pressure.
To provide this, we could:
* add a param to deactivate the check on the number of unacked messages sent (or maybe have one distinct from `receiverQueueSize` and that can be set to 0-infinity)
* add a field in `ConsumerAck` to allow more messages from the proxy (permits ?).
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services