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 Sat, 29 Apr 2017 12:48:04 GMT

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

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

[~kvr] please don't get this discussion wrong. I think we agree that having the offset available
may be useful in certain situations, we are really just quibbling about the API.

One reason why I am reluctant to adding the information to {{ArchiveEntry}} is that it is
an interface that may get implemented outside of Commons Compress itself. I know I've once
started to create an implementation for RAR that I never got far enough to contribute it to
the java rar library (who's license wouldn't allow us to host the code at Apache). If possible
I don't want to touch the interface if there is a different solution as we'd be breaking backwards
compatibility for people extending Compress.



> 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