-
Notifications
You must be signed in to change notification settings - Fork 207
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
zstd support #34
Comments
@gvollant: zstd has apparently been fixed after those fallouts. I've experimentally restored support just recently in e806006. It's now enabled in the alternate build called "big". It adds 150 KB (which is lower than in some pre-1.5.0 versions). Every dependency is an extra weight/attention/time to carry, so is zstd support "common enough" on the server side to justify it? (I mean outside facebook properties) (Moving brotli support to the "big" builds is also on the map, as I feel it doesn't contribute much in practice.) |
I confirm that
|
@vszakats I understand the weight attention, but I think there is a "chicken and egg" problem between server and client for zstd (and brotli) support. So it'll be great if brotli and zstd came back on the standard windows binary distributed on the curl website. By example, an experimental zstd nginx support was written before curl support zstd. |
Bring back zstd support in sync with brotli, enabling it in default builds. It is disabled in smaller-footprint builds and when building with -nozstd. Reported-by: Gilles Vollant Closes #34
I've (re-)enabled zstd in default builds. Hoping this helps a little bit in server-side adoption. |
Hello
commit 6318ab3 removed zstd support with this text:
@Cyan4973 @felixhandte do you have an idea on the problem ?
I was very happy to see the windows build of curl comiled with zstd 1.5.0
The text was updated successfully, but these errors were encountered: