Felix Handte

IIUC, the diff in possible output is specific to the range `14 < windowLog

@luzeagithub, although the zstd codebase can compress arbitrarily large inputs, and although the Zstd format specification allows arbitrarily distant matches, this codebase internally uses 32 bit integers to represent match...

Specifying a hard limit on the window size for HTTP transfers is not a good solution, IMHO. A global limit that is conservative enough to be of use to resource-constrained...

I spoke to a couple people and it sounds like this would be relatively straightforward to specify. I've just spun up a thread on the IETF httpbis mailing list to...

Hi @ricea, Yeah, since it turned out that the accept-encoding header does not permit sub-options other than `q=`, we would have to introduce a whole new header to do any...

Hey all, here's what we came up with: In [RFC 8878 Section 3.1.1.1.2. Window Descriptor](https://datatracker.ietf.org/doc/html/rfc8878#name-window-descriptor): ``` For improved interoperability, it's recommended for decoders to support values of Window_Size up to...

@klauspost, I see your point. I can also add decoder requirements specific to the web. Something like "Decoders handling web content must support a Window_Size of at least 8 MB."...

[RFC 9659](https://www.rfc-editor.org/rfc/rfc9659.html) shipped! And #4261 will give users ways to enforce that their compression conforms to that requirement. So I think we can finally close this.

cc @pmeenan, @nidhijaju. We'd talked about this being desirable for adoption of `dcz`. Take a look and make sure it meets your needs? It should go out in the next...

I agree that it would have been more expedient to just put it in the `CCtxParams`, but it seems bad to separate these highly interdependent variables. In this future where...