Thank you Carl for a quick response. I will try out your suggestion. On Wednesday, August 1, 2018 at 12:29:28 PM UTC-7, Carl Mastrangelo wrote: > > There is no error checking in plaintext mode. The gzip compressor is > experimental in API, but not in wireformat. You could use your own > compressor (or any data transform, such as appending a checksum) on the > data to get. > > That said, TLS provides this for you already. It might be easier to just > use self signed certs and ignore checking the CA, as TLS is pretty fast. > (faster than gzip). > > On Tuesday, July 31, 2018 at 4:53:34 PM UTC-7, Srujan Narkedamalli wrote: >> >> Hi, >> >> When using gRPC with plain text and without any compression, is there any >> error detection mechanism in gRPC (in addition to TCP CRC) to check whether >> payloads were corrupted during transport? >> >> Also, I see that gzip compression API in callOptions is marked as >> experimental API. Are there any plans to support it for production use in >> next few releases? >> Thanks, >> Srujan >> >
-- 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/f595ae24-4530-4bf0-af93-c0c7bd1f1382%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
