Lines Matching refs:method

84 Our first step is to define the gRPC *service* and the method *request* and *response* types using
105 types. gRPC lets you define four kinds of service method, all of which are used in the `RouteGuide`
117 no more messages. As you can see in our example, you specify a server-side streaming method by
129 all and return its response. You specify a client-side streaming method by placing the `stream`
142 this type of method by placing the `stream` keyword before both the request and the response.
376 Let's look at the simplest method first, `get_feature`, which just gets a `tonic::Request<Point>`
428 Now let's look at something a little more complicated: the client-side streaming method
430 with information about their trip. As you can see, this time the method receives a
624 Calling the simple RPC `get_feature` is as straightforward as calling a local method:
640 We call the `get_feature` client method, passing a single `Point` value wrapped in a
644 Here's where we call the server-side streaming method `list_features`, which returns a stream of
681 We use the `message()` method from the `tonic::Streaming` struct to repeatedly read in the
686 The client-side streaming method `record_route` takes a stream of `Point`s and returns a single
729 a stream suitable for passing into our service method. The resulting stream is then wrapped in a
735 Finally, let's look at our bidirectional streaming RPC. The `route_chat` method takes a stream