Looking at the implementation, this inherits from
::grpc::protobuf::io::ZeroCopyOutputStream,
which implies a dependency on protobuf.
Is that the case?
* If so, should this be called, say, GrpcProtoBufferReader instead?
* If this isn't used by the client of gRPC, can building and linking
with proto be omitted?
As someone who uses gRPC with a different serialization library, I'd like
to be able to not have to build or link with protobuf unless I'm using
things explicitly implemented in terms of proto messages, like channel
tracing.
--
Christopher Warrington
Microsoft Corp.
--
You received this message because you are subscribed to the Google Groups
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/grpc-io.
To view this discussion on the web visit
https://groups.google.com/d/msgid/grpc-io/eed8c0b6-2c49-454c-b3c8-8c622d879a9d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
