protobuf rpc how to let the c++ client and python server can work with
protobuf rpc?
--
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...
Since this feature is never going to be exposed, what advice do you have
for people who are using this feature and want to migrate to v3? Also, what
can we do as users to skip encoding certain fields with the new library?
Thanks,
On Tue, Jan 13, 2015 at 3:10 PM, Feng Xiao wrote:
>
>
> On Tue, J
On Tue, Jan 13, 2015 at 3:05 PM, Arjun Satish
wrote:
> Feng,
>
> What do you mean when you say "In C++/Java/Python where we support both
> proto2 and proto3, default values will continue to exist"?
>
What I meant is that you can still find its traces in the implementation
but the feature itself i
Feng,
What do you mean when you say "In C++/Java/Python where we support both
proto2 and proto3, default values will continue to exist"? When I run
protoc (v3) with the syntax="proto3" tag, it shows an error "Explicit
default values are not allowed in proto3." and exits (no code is
generated). Thi
On Mon, Jan 12, 2015 at 10:40 PM, Arjun Satish
wrote:
> Would it be possible to re-introduce this feature in a subsequent release?
> It seems like you are still using it under-the-hood.
>
In C++/Java/Python where we support both proto2 and proto3, default values
will continue to exist. In new lan
