commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Bodewig (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COMPRESS-390) Expose zip stream offset and size via API
Date Fri, 28 Apr 2017 04:12:04 GMT

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

Stefan Bodewig commented on COMPRESS-390:
-----------------------------------------

Hmm, if I understand your use case correctly you will never need the location of the header
at all, only the offset of data. In addition this really only is relevant for zip and 7z which
provide random access to entries as opposed to a forward-only stream. Would it make sense
to add a new interface only implemented by the two formats in question? We know we will never
provide an implementation for tar/ar/cpio.

> 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)

Mime
View raw message