[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jakarta-commons-dev
Subject:    [jira] [Commented] (COMPRESS-390) Expose zip stream offset and size via API
From:       "Zbynek Vyskovsky (JIRA)" <jira () apache ! org>
Date:       2017-04-30 5:02:04
Message-ID: JIRA.13066921.1493176170000.86740.1493528524074 () Atlassian ! JIRA
[Download RAW message or body]


    [ https://issues.apache.org/jira/browse/COMPRESS-390?page=com.atlassian.jira.plugi \
n.system.issuetabpanels:comment-tabpanel&focusedCommentId=15990125#comment-15990125 ] \


Zbynek Vyskovsky commented on COMPRESS-390:
-------------------------------------------

Thanks, Stefan.

About the name - could be, I'll check with my native English colleagues before \
submitting :-)


> 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, github-import, patch
> 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)


[prev in list] [next in list] [prev in thread] [next in thread]