[
https://issues.apache.org/jira/browse/COMPRESS-540?focusedWorklogId=511514&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-511514
]
ASF GitHub Bot logged work on COMPRESS-540:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 13/Nov/20 19:37
Start Date: 13/Nov/20 19:37
Worklog Time Spent: 10m
Work Description: theobisproject commented on pull request #113:
URL: https://github.com/apache/commons-compress/pull/113#issuecomment-726993226
Is anybody able to give me an information how we will progress with this
change?
As I currently understand you wanted to hear for more feedback about this
changes. Since I will have to do quite some work with the removal of code
duplication I'd like to know how long you are willing to wait for feedback.
Also it would be good to get a review of the current state of the changes to
guide me into the right direction with the refactorings which need to be done.
I will keep backporting changes from master regarding the
TarArchiveInputStream and fix bugs found in the implementation in the meantime
since I would like to avoid heading into the wrong direction with any further
changes.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 511514)
Time Spent: 3h (was: 2h 50m)
> Random access on Tar archive
> ----------------------------
>
> Key: COMPRESS-540
> URL: https://issues.apache.org/jira/browse/COMPRESS-540
> Project: Commons Compress
> Issue Type: Improvement
> Reporter: Robin Schimpf
> Priority: Major
> Time Spent: 3h
> Remaining Estimate: 0h
>
> The TarArchiveInputStream only provides sequential access. If only a small
> amount of files from the archive is needed large amount of data in the input
> stream needs to be skipped.
> Therefore I was working on a implementation to provide random access to
> TarFiles equal to the ZipFile api. The basic idea behind the implementation
> is the following
> * Random access is backed by a SeekableByteChannel
> * Read all headers of the tar file and save the place to the data of every
> header
> * User can request an input stream for any entry in the archive multiple
> times
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
