Github user kvr000 commented on the issue:
https://github.com/apache/commons-compress/pull/21
Additionally, I was thinking about exposing the entry raw stream starting
offset and length via public API so in case of need one can either map it into
memory, directly access the raw data (especially useful when zip is just kind
of flat storage, being quite popular in games but not only). For me it would
help to implement off-heap read-only storage, using standard file format widely
supported by lot of tools.
It's quite zip specific (although can be applied to similar containers too)
but anyway the API already has lot of zip specific stuff... That piece of
information would have to be only moved from ZipFile.Entry to ZipFileEntry.
What do you think about it?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
