-
Notifications
You must be signed in to change notification settings - Fork 15
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
[Feature Request]: SeekableXZInputStream ability to write straight into java.nio.ByteBuffer #2
Comments
Hi! Thank you for the feature request. Unfortunately, this is the wrong repository for this since this is XZ Utils (the C version). XZ for Java has not been moved to GitHub yet, so the code repository is still located at https://git.tukaani.org/xz-java.git. So, until we move XZ for Java to GitHub, you will need to request features or report bugs either to xz@tukaani.org or the xz-devel mailing list. Instructions for subscribing to the mailing list are documented here: https://tukaani.org/xz/lists.html. You do not need to subscribe to the mailing list to email xz@tukaani.org, but then only the maintainers will be able to see your mails. Thanks again for the feature request! |
Now that the XZ for Java repository has officially moved to GitHub this issue has been moved and reopened. This isn't a promise that we will implement the feature, just that we are considering it now. |
Is the ask here to implement ReadableByteChannel? |
I still haven't really looked into this. SeekableByteChannel would be a standard interface so perhaps that could be valuable? All internal APIs use streams and I suppose it doesn't make sense to change that. So ByteChannel support would be some sort of thin wrapper. |
Describe the Feature
Can you please add methods in SeekableXZInputStream ability to write straight into an existing java.nio.ByteBuffer
This is to replicate something like
Expected Complications
ByteBuffer is available since old versions of java, so adding this feature should not be an issue.
Will I try to implement this new feature?
No
The text was updated successfully, but these errors were encountered: