Re: [w3ctag/design-reviews] jxl Content-Encoding (#541)

Note that `Content-Encoding` is a property of the payload, so saving-as will save the `jxl` version, as opposed to `Transfer-Encoding` which has the drawback of being hop-by-hop. So you will probably need a specific 'save-as after resolving content-encoding' while brunsli is available everywhere.

Also conneg done via plugins like that are often either not really doing a proper job, as they don't have access to all the axis available for content negotiation, so listing those plugins as "pros" is debatable.

The real "pro" is that the jpeg/jxl/jpeg conversion is lossless, and that is only what matters when asking for a new content coding, even if it is not generic but tight to a specific media type (there are some examples in the [IANA listing of content codings](https://www.iana.org/assignments/http-parameters/http-parameters.xhtml))

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/541#issuecomment-674920441