Lines Matching refs:compression

10 compression supported by gRPC acts _at the individual message level_, taking
14 The implementation supports different compression algorithms. A _default
15 compression level_, to be used in the absence of message-specific settings, MAY
18 The ability to control compression settings per call and to enable/disable
19 compression on a per message basis MAY be used to prevent CRIME/BEAST attacks.
20 It also allows for asymmetric compression communication, whereby a response MAY
26 appropriate API method. There are two scenarios where compression MAY be
29 +  At channel creation time, which sets the channel default compression and
30    therefore the compression that SHALL be used in the absence of per-RPC
31    compression configuration.
35       configuration is reduced to disabling compression altogether.
39 A gRPC peer MAY choose to respond using a different compression method to that
40 of the request, including not performing any compression, regardless of channel
41 and RPC settings (for example, if compression would result in small or negative
50 compression. Data sent from a server compressed with an algorithm not supported
65 compression the next message MUST be sent uncompressed. This is instrumental in
83 in the future. Currently however, compression levels are only supported at the
89 The inheritance of the compression configuration by child RPCs is left up to the
95 1. When a compression level is not specified for either the channel or the
98 1. When per-RPC compression configuration isn't present for a message, the
99 channel compression configuration MUST be used.
100 1. When a compression method (including no compression) is specified for an
105 `grpc-accept-encoding` header MUST NOT contain the compression method
110 `grpc-accept-encoding` header MUST NOT contain the compression method