From 546e42fdd2ae111655baa9b146fe590812b0faad Mon Sep 17 00:00:00 2001 From: Abhishek Kumar Date: Thu, 22 Jan 2015 10:20:36 -0800 Subject: [PATCH] Update README.md Added a short blurb on flow control. --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 4ee4c573d6c..9e8b8e77917 100644 --- a/README.md +++ b/README.md @@ -69,5 +69,5 @@ A gRPC RPC comprises of a bidirectional stream of messages, initiated by the cli ## Implementation over HTTP/2 The abstract protocol defined above is implemented over [HTTP/2](https://http2.github.io/). gRPC bidirectional streams are mapped to HTTP/2 streams. The contents of `Call Header` and `Initial Metadata` are sent as HTTP/2 headers and subject to HPAC compression. `Payload Messages` are serialized into a byte stream of length prefixed gRPC frames which are then fragmented into HTTP/2 frames at the sender and reassembled at the receiver. `Status` and `Trailing-Metadata` are sent as HTTP/2 trailing headers (a.k.a., trailers). - -**TODO(a11r): Add a section on flow control.** +## Flow Control +gRPC inherits the flow control mchanims in HTTP/2 and uses them to enable fine-grained control of the amount of memory used for buffering in-flight messages.