Hi,
There is issue in protobuf where nested messages (recursion) if goes beyond
100 depth, DeSerialization fails. However it can be fixed via converting
serialized message into input coded stream and then setting recursion limit
and then doing DeSerialization.
Now same issue exists in GRPC, when server respond back with deep nested
message over protobuf response, client doesn't understand the response and
DeSerialization fails.
How can I access Raw Data in GRPC service call ? I have tried custom
interceptor, SerializationTraits but it doesn't seem to work.
Example PB
service RecursionTest {
rpc GetMeRecursiveProto(Req) returns (Response) {}
}
message Req {
int64 level=1;
}
message msg {
string name=1;
}
message final {
msg first=1;
int64 level=2;
repeated final inner=3;
}
message Response {
final resp = 1;
}
--
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 grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/grpc-io/e86b880b-cd1c-444a-9f7f-b7ec1a27314bn%40googlegroups.com.
