Summary
In this chapter, you learned that gRPC supports four types of calls – unary, client streaming, server streaming, and bi-directional streaming. You learned that in a Protobuf definition, the type of the call is controlled by the stream
keyword or a lack thereof.
We looked at the server-side method signatures that are used for implementing gRPC calls of different kinds. Each of these signatures includes the context
parameter, as well as the actual request and response data. This parameter is used for extracting metadata from the call, which may include user information and request headers.
You also learned that a gRPC channel can be configured by using the GrpcChannelOptions
object. This object allows you to restrict the message's size, reuse HttpClient
, apply any custom middleware logic, and more.
We also looked at what happens when multiple gRPC implementations correspond to the same HTTP path. If those paths have identical service
and rpc
names, an error...