@@ -45,7 +45,7 @@ service EchoService {
45
45
}
46
46
```
47
47
48
- The layout of generated code might be :
48
+ The layout of generated code:
49
49
50
50
```
51
51
.
@@ -60,7 +60,7 @@ The layout of generated code might be:
60
60
└── k-echo.go
61
61
```
62
62
63
- The handler code in server side might be :
63
+ The handler code on server side:
64
64
65
65
``` go
66
66
package main
@@ -93,7 +93,7 @@ func main() {
93
93
94
94
#### PingPong
95
95
96
- The code in client side might be :
96
+ The code on client side:
97
97
98
98
``` go
99
99
package main
@@ -120,7 +120,7 @@ func main() {
120
120
121
121
#### Oneway
122
122
123
- The code in client side might be :
123
+ The code on client side:
124
124
125
125
``` go
126
126
package main
@@ -147,12 +147,12 @@ func main() {
147
147
148
148
## Protobuf
149
149
150
- Kitex supports two kind of protocols that carries Protobuf payload:
150
+ Kitex supports two kinds of protocols that carry Protobuf payload:
151
151
152
152
- Kitex Protobuf
153
153
- Only supports the PingPong type of messages. If any streaming method is defined in the IDL, the protocol will switch to gRPC.
154
154
- The gRPC Protocol
155
- - The protocol that shipped with gRPC.
155
+ - Be able to interoperate with gRPC. Use the same definition as gRPC service, and supports Unary (PingPong) and Streaming calls .
156
156
157
157
### Example
158
158
@@ -182,7 +182,7 @@ service EchoService {
182
182
}
183
183
```
184
184
185
- The generated code might be :
185
+ The generated code:
186
186
187
187
```
188
188
.
@@ -196,7 +196,7 @@ The generated code might be:
196
196
└── server.go
197
197
```
198
198
199
- The handler code in server side:
199
+ The handler code on server side:
200
200
201
201
``` go
202
202
package main
0 commit comments