wip: zstd compression codec #159
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
I've started to work on adding zstd support but it turns out it's vastly more complicated than the previous compression codecs since it requires implementing several things:
I've started implementing some stuff but before going further I have some questions:
Conn.ReadBatchfor me to know if I should make a v10 request because the user wants zstd or not as far as I can see because the ConnConfig does not have any compression configuration. Should I just had it there or do you have another idea ?Conn.WriteCompressedMessagesso here I could switch request and response version based on it but again, is there a better alternative ?Anyway, I originally thought this would be an easy thing to add so I can get accustomed to the codebase, clearly I was mistaken :)