[Java] http: Jetty server sending compressed Arrow data #38
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
felipecrv
changed the title
felipecrv
changed the title
Member
|
@felipecrv #35 is merged; please rebase. Thanks! |
felipecrv
force-pushed
the
java_compression
branch
from
6eaba26 to
1267ee5
Compare
Member
|
@felipecrv could you please add a REAMDE.md like with the other examples? Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Like in the Python example I'm trying to show how both IPC buffer compression and HTTP stream compression can be negotiated with the client to maximize the chances of clients getting compressed data even when their support of the compression formats is reduced.