Searched refs:RouteSummary (Results 1 – 3 of 3) sorted by relevance
| /tonic/examples/proto/routeguide/ |
| H A D | route_guide.proto | 44 // RouteSummary when traversal is completed.
45 rpc RecordRoute(stream Point) returns (RouteSummary) {}
93 // A RouteSummary is received in response to a RecordRoute rpc.
98 message RouteSummary { message
|
| /tonic/examples/src/routeguide/ |
| H A D | server.rs | 12 use routeguide::{Feature, Point, Rectangle, RouteNote, RouteSummary};
67 ) -> Result<Response<RouteSummary>, Status> { in record_route() argument
72 let mut summary = RouteSummary::default(); in record_route()
|
| /tonic/examples/ |
| H A D | routeguide-tutorial.md | 133 // RouteSummary when traversal is completed.
134 rpc RecordRoute(stream Point) returns (RouteSummary) {}
206 - Struct definitions for message types `Point`, `Rectangle`, `Feature`, `RouteNote`, `RouteSummary`.
255 use routeguide::{Feature, Point, Rectangle, RouteNote, RouteSummary};
290 ) -> Result<Response<RouteSummary>, Status> {
429 `record_route`, where we get a stream of `Point`s from the client and return a single `RouteSummary`
442 ) -> Result<Response<RouteSummary>, Status> {
445 let mut summary = RouteSummary::default();
472 `record_route` is conceptually simple: we get a stream of `Points` and fold it into a `RouteSummary…
474 When there are no more `Points` in our stream, we return the `RouteSummary` wrapped in a
[all …]
|