Hi everyone,
the recommended way to define messages for a RPC call is to append
"Request" and "Response" to the name of the Rpc.
A colleague proposed an alternative solution by using nested messages
instead.
So he proposed to use the following structure
service Service {
rpc Foo(Foo.Request) returns (Foo.Response) {}
}
message Foo {
enum {
// enum declarations
}
message Request {
// Parameters
}
message Response {
}
}
IMHO a clever solution where the enum declarations are local to the call as
well..
Any reasons NOT to use this structure?
Thanks for your feedback
Tobias
--
You received this message because you are subscribed to the Google Groups
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/grpc-io/25a6fadd-7391-43d1-b6b7-0392d02b92e5n%40googlegroups.com.
