On Sat, Jun 29, 2019 at 5:22 AM Ananya Bhat <ananyabha...@gmail.com> 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 then it would also be difficult to change the API over time, whereas with messages it's easy to add new fields. > How partial messages can be explicitly specified in service RPCs without > using nesting? > As far as I know there is no way to specify partial messages in the service schema. However, you can always specify the full message with the understanding that it won't necessarily have a value set in every field. -- 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 protobuf+unsubscr...@googlegroups.com. To post to this group, send email to protobuf@googlegroups.com. Visit this group at https://groups.google.com/group/protobuf. To view this discussion on the web visit https://groups.google.com/d/msgid/protobuf/CADqAXr5c0Ld17RJBnC%3DVTRji9pwYYtGzVdWjRvmzQdGKDfBr6Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
