RpcSystem::setFlowLimit() should work for this. Yes, this means the RPC
system will stop reading messages from the socket buffer if too many
requests are in flight. That will naturally cause TCP backpressure to kick
in. However, buffering still could happen on the client side if the client
isn't
Hi,
I am trying to setup an rpc server in order to integrate it into my custom
publisher-subscriber library. For this I need a flow control mechanism that
doesn't depend on individual streams but on a global disk writing speed.
That is: The flow limit should adapt to the in-flight-bytes of the
