There's no distinction between
message Foo {
int32 foo = 1;
}
and
message Bar {
int32 bar = 1;
}
It's all encoded as tags and values, the type and field names aren't
on the wire. Unknown tags are ignored (or put into a "unknown tag"
list). The framing is entirely up to you. One non-horrible
I'm using the MOOS communications framework, which allows me to send
messages between modules in a binary, string, or numerical format using a
centralized database. In order to minimize the number of new interfaces
that I need to create, I'd like to send multiple messages over the same
interfac
On Mon, Apr 30, 2018 at 10:57 AM, 'Feng Xiao' via Protocol Buffers <
protobuf@googlegroups.com> wrote:
> On Mon, Apr 30, 2018 at 6:37 AM Gary Pennington wrote:
>
>> This is probably a silly question, but:
>>
>> "Is protocol buffers language 3 a finished specification?"
>>
>> At various points on
On Mon, Apr 30, 2018 at 6:37 AM Gary Pennington wrote:
> This is probably a silly question, but:
>
> "Is protocol buffers language 3 a finished specification?"
>
> At various points on the gRPC pages, e.g.:
> https://grpc.io/docs/tutorials/basic/java.html, the text specifically
> mentions that "t
This is probably a silly question, but:
"Is protocol buffers language 3 a finished specification?"
At various points on the gRPC pages,
e.g.: https://grpc.io/docs/tutorials/basic/java.html, the text specifically
mentions that "the proto3 version of the protocol buffers language, which
is curre
