Joakim Erdfelt

This seems out of date

Biggest issue is the lack of a performant Java implementation of brotli.

While decompression is reported to be better, the encoding is still very slow. Dynamic encoding/compression with brotli is still something that requires more improvements/experimentation before it will be widely adopted....

Before Jetty can use the `jvm-brotli` project (mentioned by @nixxcode) the license needs to be properly identified. I opened an issue there for the licensing issue https://github.com/nixxcode/jvm-brotli/issues/44 Once that is...

@tipsy shame, as we would be force to remove it from Jetty as it's abandonware due to various corporate policies around this kind of thing. Is there a fork of...

The google brotli lib is only at 0.1.2 on maven central. https://search.maven.org/artifact/org.brotli/dec And hasn't seen a release since May 2017 Meanwhile, the main codebase still chugs on, all the way...

Tip: the label `Pinned` will prevent issues from going stale.

The details on caniuse.com are the other way around for the fundamental Content-Encoding behaviors. 100% for gzip 95.2% for brotli

The other hard part is the Brotli Java support. Which, last time we investigated this we hit the following issues. * Wasn't 100% java (it had required native libs) *...

See also tasks in #5748