diff options
| author |  David Garcia Quintas <dgq@google.com> | 2016-06-21 11:52:29 -0700 |
|---|---|---|
| committer | David Garcia Quintas <dgq@google.com> | 2016-06-21 11:52:29 -0700 |
| commit | b665dd2722371e5c4a28bbf6cb5f791f8ab5cca9 (patch) | |
| tree | e571a7f998ef1e00224cefb362ef9e9cb08f995a | |
| parent | 9f26a149a5da48364ec62dd607e34104bb851c6d (diff) | |
reworded some
| -rw-r--r-- | doc/compression.md | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/doc/compression.md b/doc/compression.md index a116ac50a1..15fae4d29b 100644 --- a/doc/compression.md +++ b/doc/compression.md @@ -42,13 +42,13 @@ and RPC settings (for example, if compression would result in small or negative gains). When a message from a client compressed with an unsupported algorithm is -processed by a server, it WILL result in an INVALID\_ARGUMENT error. The server -will include in its response a `grpc-accept-encoding` header specifying the -algorithms it does accept. If an INTERNAL error is returned from the server -despite having used one of the algorithms from the `grpc-accept-encoding` -header, the cause MUST NOT be related to compression. Data sent from a server -compressed with an algorithm not supported by the client WILL result in an -INTERNAL error on the client side. +processed by a server, it WILL result in an INVALID\_ARGUMENT error on the +server. The server will then include in its response a `grpc-accept-encoding` +header specifying the algorithms it does accept. If an INTERNAL error is +returned from the server despite having used one of the algorithms from the +`grpc-accept-encoding` header, the cause MUST NOT be related to compression. +Data sent from a server compressed with an algorithm not supported by the client +WILL result in an INTERNAL error on the client side. Note that a peer MAY choose to not disclose all the encodings it supports. However, if it receives a message compressed in an undisclosed but supported |