diff options
author | Abhishek Kumar <abhikumar@google.com> | 2015-01-22 10:20:36 -0800 |
---|---|---|
committer | Abhishek Kumar <abhikumar@google.com> | 2015-01-22 10:20:36 -0800 |
commit | 546e42fdd2ae111655baa9b146fe590812b0faad (patch) | |
tree | b512892ee65b0a8fe2960ddf5cefa069f1da4cb8 | |
parent | bb20de4c3f0a03d4206d3fb1434c67b0ea514398 (diff) |
Update README.md
Added a short blurb on flow control.
-rw-r--r-- | README.md | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -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. |