Struct grpcio::ChannelBuilder[][src]

pub struct ChannelBuilder { /* fields omitted */ }

Channel configuration object.

Methods

impl ChannelBuilder
[src]

The caller of the secure_channel_create functions may override the target name used for SSL host name checking using this channel argument. This should be used for testing only.

impl ChannelBuilder
[src]

Default authority to pass if none specified on call construction.

Maximum number of concurrent incoming streams to allow on a http2 connection.

Maximum message length that the channel can receive. usize::MAX means unlimited.

Maximum message length that the channel can send. -1 means unlimited.

The maximum time between subsequent connection attempts.

The time between the first and second connection attempts.

Initial sequence number for http2 transports.

Amount to read ahead on individual streams. Defaults to 64kb, larger values can help throughput on high-latency connections.

Primary user agent: goes at the start of the user-agent metadata sent on each request.

If enable, allow the use of SO_REUSEPORT if it's available (default true).

How large a slice to try and read from the wire each time.

How minimal large a slice to try and read from the wire each time.

How maximal large a slice to try and read from the wire each time.

How much data are we willing to queue up per stream if write_buffer_hint is set. This is an upper bound.

How big a frame are we willing to receive via HTTP2. Min 16384, max 16777215. Larger values give lower CPU usage for large messages, but more head of line blocking for small messages.

Set BDP probing.

Minimum time between sending successive ping frames without receiving any data frame.

Minimum allowed time between receiving successive ping frames without sending any data frame.

How many pings can we send before needing to send a data frame or header frame? (0 indicates that an infinite number of pings can be sent without sending a data frame or header frame)

How many misbehaving pings the server can bear before sending goaway and closing the transport? (0 indicates that the server can bear an infinite number of misbehaving pings)

Default compression algorithm for the channel.

Default compression level for the channel.

After a duration of this time the client/server pings its peer to see if the transport is still alive.

After waiting for a duration of this time, if the keepalive ping sender does not receive the ping ack, it will close the transport.

Is it permissible to send keepalive pings without any outstanding streams.

Optimize a channel.

Default is OptTarget::Blend.

Build a channel args from the current configuration.

Build an insure connection to the address.

Auto Trait Implementations