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
It is common to exclude already compressed data from a secound pass in wire and/or persistent storage.
One of the oldest example would be the exlusion of http gzip comp. For jpeg/PNG files.
It would be a good idea to include a well-known msg header to mark a msg data as compressed.
Even if it is not instantly used by the server components, it will have its usage in the feature.
One of main benefit of handle compressed data exclusively, beside less processing req, is that the compressed data will not poison the compression stream/dictionary
Because the marker would be also valid for encrypted data, the header should mark a message uncompressable.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
It is common to exclude already compressed data from a secound pass in wire and/or persistent storage.
One of the oldest example would be the exlusion of http gzip comp. For jpeg/PNG files.
It would be a good idea to include a well-known msg header to mark a msg data as compressed.
Even if it is not instantly used by the server components, it will have its usage in the feature.
One of main benefit of handle compressed data exclusively, beside less processing req, is that the compressed data will not poison the compression stream/dictionary
Because the marker would be also valid for encrypted data, the header should mark a message uncompressable.
Example: x-nats-flags: nocomp
Beta Was this translation helpful? Give feedback.
All reactions