On Sat, Jun 29, 2019 at 5:22 AM Ananya Bhat wrote:
>
> Please clarify the following
> Why scalar types can not be used as IN parameter or OUT parameters of
> Service RPCs?
>
I think it just simplifies everything to use message types only. If we
allowed non-message types as requests or responses
Hi,
I am new to protobuf.
I have question related to similar usecase.
Please clarify my doubts to decide better message specification
I have definition something like below
Option A
message Student
{
message Empty
{
}
//Name of the Student
optional string name = 1;
// Year of Passing
optional s
Hello,
I have similar question related to using message types with string fields
e.g.
message Document
{
On Tuesday, September 25, 2018 at 6:41:46 PM UTC+5:30, omid pourhadi wrote:
>
> Hi,
>
> I'm new to protobuf and I'm trying to create a simple CRUD app with grpc
> my proto file is :
>
>
A message type is required for both the request and response. You can
always use google.protobuf.Empty (from src/google/protobuf/empty.proto) as
a placeholder empty message.
On Tue, Sep 25, 2018 at 6:23 AM omid pourhadi
wrote:
> and sometimes I don't want to pass any message type to rpc method
>
and sometimes I don't want to pass any message type to rpc method
rpc count() returns (int32 count) {};
--
You received this message because you are subscribed to the Google Groups
"Protocol Buffers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
