Currently the only flow control in grapesy is implicit: we currently use a one-place buffer for incoming and outgoing messages, providing backpressure in both directions. It might at least make sense to generalize this, for example for better latency masking. (Some discussion of buffering in https://medium.com/engineering-at-palo-alto-networks/dataflow-and-grpc-using-at-scale-9612303dfe0b.)
Main reference https://grpc.io/docs/guides/flow-control/ .
Note that HTTP2 flow control is implemented by the
http2package, withgrapesyis based on.Additional references:
Currently the only flow control in
grapesyis implicit: we currently use a one-place buffer for incoming and outgoing messages, providing backpressure in both directions. It might at least make sense to generalize this, for example for better latency masking. (Some discussion of buffering in https://medium.com/engineering-at-palo-alto-networks/dataflow-and-grpc-using-at-scale-9612303dfe0b.)Potentially related: #117 .