You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 22, 2020. It is now read-only.
Have you thought about creating a multi-architecture jar and at init time look at the current architecture and load that native library?
zstd-jni and lz4-java do this. This turns it into one big jar instead of several jars. This in turn simplifies releases of applications that use jbrotli.
For the furture, for unsupported platforms, we could use the java decoder implementation that has surfaced in the brotli repo. Would be a nice fallback.
The text was updated successfully, but these errors were encountered:
+1 for it.
And also can we have brotli packaged as a static lib? Just like netty-tcnative-boringssl-static (http://netty.io/wiki/forked-tomcat-native.html), so we do not have to worry about platform library versions.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Have you thought about creating a multi-architecture jar and at init time look at the current architecture and load that native library?
zstd-jni and lz4-java do this. This turns it into one big jar instead of several jars. This in turn simplifies releases of applications that use jbrotli.
For the furture, for unsupported platforms, we could use the java decoder implementation that has surfaced in the brotli repo. Would be a nice fallback.
The text was updated successfully, but these errors were encountered: