Lines Matching refs:s

25 any of gRPC's supported languages, which in turn can be run in environments ranging from servers
39 Clone or download Tonic's repository:
45 Change your current directory to Tonic's repository root:
65 … location: Some(Point { latitude: 409146139, longitude: -746188906 }), message: "at 1.000319208s" }
85 [protocol buffers]. We will keep our `.proto` files in a directory in our crate's root.
150 response types used in our service methods - for example, here's the `Point` message type:
166 Tonic can be configured to generate code as part cargo's normal build process. This is very
204 That's it. The generated code contains:
217 First let's look at how we create a `RouteGuide` server. If you're only interested in creating gRPC
247 We can use Tonic's `include_proto` macro to bring the generated code into scope:
335 **Note:** If you are following along, you'll need to change the data file's path  from
376 Let's look at the simplest method first, `get_feature`, which just gets a `tonic::Request<Point>`
394 Now let's look at one of our streaming RPCs. `list_features` is a server-side streaming RPC, so we
395 need to send back multiple `Feature`s to our client.
419 Like `get_feature`, `list_features`'s input is a single message, a `Rectangle` in this
428 Now let's look at something a little more complicated: the client-side streaming method
429 `record_route`, where we get a stream of `Point`s from the client and return a single `RouteSummary`
478 Finally, let's look at our bidirectional streaming RPC `route_chat`, which receives a stream
479 of `RouteNote`s and returns  a stream of `RouteNote`s.
612 create a client in our main function, passing the server's full URL to `RouteGuideClient::connect`.
620 Now let's look at how we call our service methods. Note that in Tonic, RPCs are asynchronous,
644 Here's where we call the server-side streaming method `list_features`, which returns a stream of
645 geographical `Feature`s.
682 server's responses to a response protocol buffer object (in this case a `Feature`) until there are
686 The client-side streaming method `record_route` takes a stream of `Point`s and returns a single
735 Finally, let's look at our bidirectional streaming RPC. The `route_chat` method takes a stream
795 Tonic's default code generation configuration is convenient for self contained examples and small