mirror of https://github.com/grpc/grpc.git
The C based gRPC (C++, Python, Ruby, Objective-C, PHP, C#)
https://grpc.io/
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
37 lines
1.0 KiB
37 lines
1.0 KiB
10 months ago
|
# Generic API Example
|
||
|
|
|
||
|
|
## Overview
|
||
|
|
|
||
|
|
While generated stub code is often the simpler and best choice for sending and handling API calls,
|
||
|
|
generic APIs offer unique advantages in specific scenarios, such as proxy implementation.
|
||
|
|
Their ability to manage multiple message types with a single function makes them particularly handy
|
||
|
|
in these cases. This example demonstrates how to use generic APIs to achieve this flexibility.
|
||
|
|
|
||
|
|
This example implements `greeter_callback_client` and `greeter_callback_server` using the generic APIs.
|
||
|
|
Therefore, looking at the difference would be helpful to understand how to use generic APIs.
|
||
|
|
|
||
|
|
### Try it!
|
||
|
|
|
||
|
|
Once you have working gRPC, you can build this example using either bazel or cmake.
|
||
|
|
|
||
|
|
Run the server, which will listen on port 50051:
|
||
|
|
|
||
|
|
```sh
|
||
|
|
$ ./greeter_server
|
||
|
|
```
|
||
|
|
|
||
|
|
Run the client (in a different terminal):
|
||
|
|
|
||
|
|
```sh
|
||
|
|
$ ./greeter_client
|
||
|
|
```
|
||
|
|
|
||
|
|
If things go smoothly, you will see the client output:
|
||
|
|
|
||
|
|
```
|
||
|
|
### Send: SayHello(name=World)
|
||
|
|
Ok. ReplyMessage=Hello World
|
||
|
|
### Send: SayHello(name=gRPC)
|
||
|
|
Ok. ReplyMessage=Hello gRPC
|
||
|
|
```
|