The compression level to use. If passed the default value (-1) then use TextualContentCompressor which will compress text-like content-types with the default compression level (6). Otherwise, use HttpContentCompressor for all content-types with specified compression level.
The maximum size of the inbound request an HTTP server constructed with
this codec can receive (default is 5 megabytes). Should be less than 2 gigabytes (up to
Int.MaxValue
bytes). Use streaming/chunked requests to handle larger messages.
The maximum size of the inbound response an HTTP client constructed with
this codec can receive (default is 5 megabytes). Should be less than 2 gigabytes (up to
Int.MaxValue
bytes). Use streaming/chunked requests to handle larger messages.
Streaming allows applications to work with HTTP messages
that have large (or infinite) content bodies. When this flag is set to
true
, the message content is available through a com.twitter.io.Reader,
which gives the application a handle to the byte stream. If false
, the
entire message content is buffered into a com.twitter.io.Buf.
The compression level to use.
The compression level to use. If passed the default value (-1) then use TextualContentCompressor which will compress text-like content-types with the default compression level (6). Otherwise, use HttpContentCompressor for all content-types with specified compression level.
The maximum size of the inbound request an HTTP server constructed with this codec can receive (default is 5 megabytes).
The maximum size of the inbound request an HTTP server constructed with
this codec can receive (default is 5 megabytes). Should be less than 2 gigabytes (up to
Int.MaxValue
bytes). Use streaming/chunked requests to handle larger messages.
The maximum size of the inbound response an HTTP client constructed with this codec can receive (default is 5 megabytes).
The maximum size of the inbound response an HTTP client constructed with
this codec can receive (default is 5 megabytes). Should be less than 2 gigabytes (up to
Int.MaxValue
bytes). Use streaming/chunked requests to handle larger messages.
Streaming allows applications to work with HTTP messages that have large (or infinite) content bodies.
Streaming allows applications to work with HTTP messages
that have large (or infinite) content bodies. When this flag is set to
true
, the message content is available through a com.twitter.io.Reader,
which gives the application a handle to the byte stream. If false
, the
entire message content is buffered into a com.twitter.io.Buf.
(Since version 2016-05-10) Use maxRequestSize to enforce buffer footprint limits
The compression level to use. If passed the default value (-1) then use TextualContentCompressor which will compress text-like content-types with the default compression level (6). Otherwise, use HttpContentCompressor for all content-types with specified compression level.
The maximum size of the inbound request an HTTP server constructed with this codec can receive (default is 5 megabytes). Should be less than 2 gigabytes (up to
Int.MaxValue
bytes). Use streaming/chunked requests to handle larger messages.The maximum size of the inbound response an HTTP client constructed with this codec can receive (default is 5 megabytes). Should be less than 2 gigabytes (up to
Int.MaxValue
bytes). Use streaming/chunked requests to handle larger messages.Streaming allows applications to work with HTTP messages that have large (or infinite) content bodies. When this flag is set to
true
, the message content is available through a com.twitter.io.Reader, which gives the application a handle to the byte stream. Iffalse
, the entire message content is buffered into a com.twitter.io.Buf.