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

List:       jakarta-commons-dev
Subject:    [jira] [Commented] (COMPRESS-320) File listing and random access of 7Z files
From:       "Dawid Weiss (JIRA)" <jira () apache ! org>
Date:       2016-02-28 19:51:18
Message-ID: JIRA.12854129.1439289605000.168122.1456689078198 () Atlassian ! JIRA
[Download RAW message or body]


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


Dawid Weiss commented on COMPRESS-320:
--------------------------------------

Oh, I didn't take it the wrong way, no worries at all. I just think it's not \
"resolvable" and I tried to explain why. It's much like the 7z format not being \
suitable for streaming decompression (because the metadata is kept at the end of the \
stream, which kind of defeats the whole idea) -- this is a "won't fix" resolution for \
me.

> File listing and random access of 7Z files
> ------------------------------------------
> 
> Key: COMPRESS-320
> URL: https://issues.apache.org/jira/browse/COMPRESS-320
> Project: Commons Compress
> Issue Type: Improvement
> Components: Archivers
> Reporter: Bill Chen
> Priority: Minor
> 
> I guess these must be one of the most wanted features and it should be very simple \
> to implement (as I have done one in 126 lines). Most (if not all) of the \
> infrastructure is already there, including an index of all files. And, with some \
> careful coding, the capability to read any of them in any order concurrently was \
> not difficult to add. My code uses loads of lambda and reflection stuff, but I am \
> happy to contribute a clean Java 5/6 implementation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


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