Re: [webkit-dev] Request for feedback on CompressionStream and DecompressionStream

We are implementing the "deflate-raw" compression codec for compression streams. This is similar to "deflate" but lacks a header and footer. In other words, it is pure RFC1951, unlike "deflate" which is actually RFC1950, "ZLIB Compressed Data Format". The awkward naming is for compatibility with

Re: [webkit-dev] Request for feedback on CompressionStream and DecompressionStream

Hi all, This is a very belated reply but what's being proposed seems reasonable to us (Apple's WebKit team). We would like to know more about use cases, and how they might be deployed in real websites / use cases but we don't see any major issues with it. - R. Niwa On Wed, Nov 27, 2019 at 11:18

Re: [webkit-dev] Request for feedback on CompressionStream and DecompressionStream

You can see DecompressionStream in action in unarchiver , this is the relevant code snippet (run it in Chrome 79+ with the

[webkit-dev] Request for feedback on CompressionStream and DecompressionStream

I am trying to gauge feedback on compression streams with a view to shipping them in Chromium. Very briefly, they are a way to do gzip and gunzip in the browser. Less briefly, the explainer https://github.com/WICG/compression/blob/master/explainer.md goes into some detail of the how and why. The