Searched refs:get_feature (Results 1 – 3 of 3) sorted by relevance
| /tonic/examples/src/routeguide/ |
| H A D | client.rs | 98 .get_feature(Request::new(Point { in main()
|
| H A D | server.rs | 27 async fn get_feature(&self, request: Request<Point>) -> Result<Response<Feature>, Status> { in get_feature() method
|
| /tonic/examples/ |
| H A D | routeguide-tutorial.md | 274 async fn get_feature(&self, _request: Request<Point>) -> Result<Response<Feature>, Status> {
376 Let's look at the simplest method first, `get_feature`, which just gets a `tonic::Request<Point>`
381 async fn get_feature(&self, request: Request<Point>) -> Result<Response<Feature>, Status> {
419 Like `get_feature`, `list_features`'s input is a single message, a `Rectangle` in this
624 Calling the simple RPC `get_feature` is as straightforward as calling a local method:
632 .get_feature(Request::new(Point {
640 We call the `get_feature` client method, passing a single `Point` value wrapped in a
|