You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/04/26 04:47:04 UTC
[jira] [Commented] (COMPRESS-390) Expose zip stream offset and size
via API
[ https://issues.apache.org/jira/browse/COMPRESS-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15984160#comment-15984160 ]
ASF GitHub Bot commented on COMPRESS-390:
-----------------------------------------
GitHub user kvr000 opened a pull request:
https://github.com/apache/commons-compress/pull/22
COMPRESS-390: Expose stream offsets and size
Pull request for https://issues.apache.org/jira/browse/COMPRESS-390
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kvr000/commons-compress feature/COMPRESS-390-expose-file-offset-via-api
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/commons-compress/pull/22.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #22
----
commit 8a6d7ecaa09c5a7386b593ac844cf97ca6b122e5
Author: Zbynek Vyskovsky <kv...@gmail.com>
Date: 2017-04-26T04:31:44Z
COMPRESS-390: Expose stream offsets and size
----
> Expose zip stream offset and size via API
> -----------------------------------------
>
> Key: COMPRESS-390
> URL: https://issues.apache.org/jira/browse/COMPRESS-390
> Project: Commons Compress
> Issue Type: New Feature
> Components: Archivers
> Affects Versions: 1.13
> Reporter: Zbynek Vyskovsky
> Labels: features
> Fix For: 1.14
>
>
> In certain cases it may be useful to get information about where in the archive the stream starts and ends. Typically when zip is used as resource container and the resources are then mapped directly into memory, but not only.
> The size and compressed size are already available but not the stream offset.
> This can be applied to other archive types as well, therefore it would make sense to put this into basic interface - ArchiveEntry. But not necessarily all of them have to support it.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)