search

WICG / compression-dictionary-transport

Other
92 stars 8 forks source link

Consider support other Content-Encoding schemes #31

Closed rektide closed 1 year ago

rektide commented 1 year ago

Hello. Could/should this specification be generalized to support it's application to other compression schemes? Currently the README seems exclusively focused on Brotli, but having wider support could help other standards.

For example there is the zstd compression scheme, here: https://docs.google.com/document/d/1aDyUw4mAzRdLyZyXpVgWvO-eLpc4ERz7I_7VDIPo9Hc/edit . This too could use Dictionary support.

Concern over handling (or lack thereof) of dictionaries was one of the primary concerns cited in mozilla/standards-positions#105 for the defer status against the zstd compression scheme proposal. If this PR could be generalized a bit, there's a possibility of zstd & potentially other compression schemes to have a better chance, to making it forward & helping users save cpu & bandwidth on the web.

pmeenan commented 1 year ago

Yep, sorry, I'll make it clearer that the dictionary negotiation is compression-agnostic and works with and content-encoding that both the browser and origin support. Brotli is meant to just be an example since it is already supported in the browsers but zstd is also expected to be supported when/if browser support is added.

We've also talked about WASM-aware content encoding that could better compress code (with awareness of address offsets) than just using a generic compression scheme.

rektide commented 1 year ago

It was great landing back on the repo & seeing things so improved. Many thanks!!