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
we should confirm that what compression we support for the regular API commands, document what we accept in the Accept header form clients and confirm we are returning data compressed if asked with the correct content type header.
And then work with the client team to see if they are requesting compression.
if there is a choice, we should get the clients to ask for the fastest compression not the most compressed. Because we are more about latency of small requests.
The outcome should be integration tests that make requests with the supported compression and verifies the results were as expected.
The text was updated successfully, but these errors were encountered:
RE: this issue quarkusio/quarkus#26112
we should confirm that what compression we support for the regular API commands, document what we accept in the Accept header form clients and confirm we are returning data compressed if asked with the correct content type header.
And then work with the client team to see if they are requesting compression.
if there is a choice, we should get the clients to ask for the fastest compression not the most compressed. Because we are more about latency of small requests.
The outcome should be integration tests that make requests with the supported compression and verifies the results were as expected.
The text was updated successfully, but these errors were encountered: