Implementation for the gRPC hello world example.
Implementation for the gRPC route guide example.
Extends the async "Hello World" example to demonstrate compression of the response body.
Extends the async "Hello World" example to demonstrate gRPC deadlines (aka timeout).
Demonstrates how to use HTTP/2 keep alive for gRPC server and client. Keep alive uses transport control frames to ensure the peer is still able to read and write to open connections. If the peer is not able to respond to the control frame within the configured amount of time, the connection is closed. This is useful if your environment doesn’t provide other forms of connection keep alive (e.g. SO_KEEPALIVE, and maybe preferred to lower level keep alive because it is closer the application logic (more likely if this check works, that your application is able to read/write). Keep alive can be helpful to detect scenarios such as non-graceful disconnects (e.g. power outage, ethernet cable pulled, buggy middle box) and general network disconnects.
This example demonstrates the following: - Use of GrpcLifecycleObserver to log a summary of each request/response.
Using the following classes:
The gRPC protocol supports propagating application level errors, and also provides serialization/deserialization of
these objects. This example demonstrates a server returning an application level error to the client via the gRPC
transport. The client intentionally omits the
token field which is required, and the server returns an application
level error. In this case the application level error type happens to be defined in
error_details.proto, but it
could be any protobuf object.
The gRPC implementation can be configured to execute all or some of the routes for a server without offloading. Using the
IoExecutor for executing routes is appropriate only if there is no possibility that the route implementation will block.
The example demonstrates the impact of different route execution strategy configuration mechanisms.
This example demonstrates how options for the servicetalk-grpc-protoc plugin can be used. See protoc-options for more details.
This example demonstrates how request and response context can be used to access HTTP meta-data.