Have you tried using https://grpc.io/? Streaming is supported there:
https://grpc.io/docs/guides/concepts/
*From: *
*Date: *Mon, May 6, 2019 at 8:27 PM
*To: *Protocol Buffers
Hi,
>
>
> this problem can be solved in below way also.
>
> 1. By defining new message type.
>
> new_message {
>
Hi,
this problem can be solved in below way also.
1. By defining new message type.
new_message {
message a1:1;
message a2:2;
...
message a32:32
}
In proto3, all the fields are optional by default.
so no need to encode everything. But the problem is we can define more then
32
On Mar 8, 2012, at 2:30 , waynix wrote:
Since this is so common an issue and the suggested solution is almost
de facto standard, (saw this after my initial post:
http://code.google.com/apis/protocolbuffers/docs/techniques.html), it
begs the question of why not build it into protobuf proper.
Thank you so much Evan for your response.
While I look at your old posts and dig into coded stream (as I said,
new to protobuf), it seems to me this approach is external to
protobuf, in the sense that I have to tell the third party what my
delimiter is (it's a length as in you sample code) or I
