@@ -67,7 +67,7 @@ Then we define `rpc` methods inside our service definition, specifying their req
67
67
68
68
``` proto
69
69
// Obtains the feature at a given position.
70
- rpc GetFeature(Point) returns (Feature) {}
70
+ rpc GetFeature(Point) returns (Feature);
71
71
```
72
72
73
73
- A * server-side streaming RPC* where the client sends a request to the server
@@ -81,7 +81,7 @@ Then we define `rpc` methods inside our service definition, specifying their req
81
81
// streamed rather than returned at once (e.g. in a response message with a
82
82
// repeated field), as the rectangle may cover a large area and contain a
83
83
// huge number of features.
84
- rpc ListFeatures(Rectangle) returns (stream Feature) {}
84
+ rpc ListFeatures(Rectangle) returns (stream Feature);
85
85
```
86
86
87
87
- A * client-side streaming RPC* where the client writes a sequence of messages
@@ -93,7 +93,7 @@ Then we define `rpc` methods inside our service definition, specifying their req
93
93
``` proto
94
94
// Accepts a stream of Points on a route being traversed, returning a
95
95
// RouteSummary when traversal is completed.
96
- rpc RecordRoute(stream Point) returns (RouteSummary) {}
96
+ rpc RecordRoute(stream Point) returns (RouteSummary);
97
97
```
98
98
99
99
- A * bidirectional streaming RPC* where both sides send a sequence of messages
@@ -108,7 +108,7 @@ Then we define `rpc` methods inside our service definition, specifying their req
108
108
``` proto
109
109
// Accepts a stream of RouteNotes sent while a route is being traversed,
110
110
// while receiving other RouteNotes (e.g. from other users).
111
- rpc RouteChat(stream RouteNote) returns (stream RouteNote) {}
111
+ rpc RouteChat(stream RouteNote) returns (stream RouteNote);
112
112
```
113
113
114
114
Our ` .proto ` file also contains protocol buffer message type definitions for all
0 commit comments