You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this issue #1704 discusses the issue of data compression. It seems that grpc does not intend to continue to do more work on data compression, but Compressor is used in MessageFramer.writeCompressed(), does grpc java encourage or allow the addition of more compression algorithms, such as brotli and zstd to improve compression performance, or continue to maintain the current compression algorithm without intending to do more work? thanks
The text was updated successfully, but these errors were encountered:
The current Compressor API can be used to add support for more compressors. Although this is specific to Java and not available in all languages (maybe just Go). That said, I think it was wrong to expose the API, but it hasn't been important enough to fight to remove it or fight to stabilize it.
If you are interested in other algorithms, especially brotli and zstd, I'd suggest you consider a cross-language effort. Brotli and zstd can be interesting for many users. There's a related discussion at grpc/grpc#26460, so I don't think you are alone.
In this issue #1704 discusses the issue of data compression. It seems that grpc does not intend to continue to do more work on data compression, but
Compressor
is used inMessageFramer.writeCompressed()
, does grpc java encourage or allow the addition of more compression algorithms, such asbrotli
andzstd
to improve compression performance, or continue to maintain the current compression algorithm without intending to do more work? thanksThe text was updated successfully, but these errors were encountered: