mirror of
https://github.com/google/brotli.git
synced 2026-09-22 06:35:52 +00:00
Publish JNI artefacts (including platform-dependent) #474
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @deshanxiao on GitHub (Aug 10, 2023).
Is it possible for us to support the java version of Brotli's encoder?
@eustas commented on GitHub (Aug 10, 2023):
Hello. Do you mean pure Java encoder?
@deshanxiao commented on GitHub (Aug 10, 2023):
Hi @eustas yes, I try to find java encoder in https://mvnrepository.com/artifact/org.brotli. But it seems that there is just a
deccomponent.@eustas commented on GitHub (Aug 10, 2023):
Unfortunately, we currently do not have pure Java encoder, but we do have plans to implement it. Generally speaking, C brotli as it is today is a collection of encoders which share some common code.
What quality range (fast, balanced, maximal density) is the primary target? Knowing that would allow us to focus on it first.
(Also I have a dream that a decent WASM runtime for JVM will arrive and it will allow easier porting of native code to Java libraries)
@deshanxiao commented on GitHub (Aug 10, 2023):
In fact, it can also be accpeted in the form of JNI if we could provide a offical jar packages and support enough system architecture (like aarch64).
Since there is no official java encoder support, we have to use a library such as https://github.com/hyperxpro/Brotli4j
It might be better if users can adjust these parameters according to their needs.
@eustas commented on GitHub (Aug 10, 2023):
Agree. We could do that much faster (and encoder will be much more performant).
I'll update issue title then.
For pure java encoder there is #405
@deshanxiao commented on GitHub (Aug 11, 2023):
Thank you @eustas! If you don't mind please let me know if there is any progress.
@deshanxiao commented on GitHub (Dec 4, 2023):
Hi @eustas Do we have any plans to implement this feature for Java users?