Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id D853D200CAA for ; Fri, 2 Jun 2017 16:18:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id D7663160BD1; Fri, 2 Jun 2017 14:18:08 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 2A0B8160BD2 for ; Fri, 2 Jun 2017 16:18:08 +0200 (CEST) Received: (qmail 82927 invoked by uid 500); 2 Jun 2017 14:18:07 -0000 Mailing-List: contact issues-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@commons.apache.org Delivered-To: mailing list issues@commons.apache.org Received: (qmail 82907 invoked by uid 99); 2 Jun 2017 14:18:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Jun 2017 14:18:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id E1712C0FC2 for ; Fri, 2 Jun 2017 14:18:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id CXX7ll9Mbmtf for ; Fri, 2 Jun 2017 14:18:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id AEA5D5FDB6 for ; Fri, 2 Jun 2017 14:18:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id E97A8E0D99 for ; Fri, 2 Jun 2017 14:18:04 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 4906C21B5F for ; Fri, 2 Jun 2017 14:18:04 +0000 (UTC) Date: Fri, 2 Jun 2017 14:18:04 +0000 (UTC) From: "Simon Spero (JIRA)" To: issues@commons.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (COMPRESS-390) Expose zip stream offset and size via API MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 02 Jun 2017 14:18:09 -0000 [ https://issues.apache.org/jira/browse/COMPRESS-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034768#comment-16034768 ] Simon Spero commented on COMPRESS-390: -------------------------------------- [~bodewig] - the XZ dependency was just the easiest hack. Annoyingly, it's an abstract class, not an interface. SeekableChannels are probably where the actual answers lie :) > 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)