You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Stefan Bodewig (JIRA)" <ji...@apache.org> on 2013/03/05 06:31:12 UTC

[jira] [Commented] (COMPRESS-220) createCompressorInputStream with decompressConcatenated option

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

Stefan Bodewig commented on COMPRESS-220:
-----------------------------------------

Yes, sounds like a good idea to enable something like this.

ArchiveStreamFactory has a setter for entry-encoding at the factory level, might be good to mirror this for the decompressConcatenated flag in CompressorStreamFactory.
                
> createCompressorInputStream with decompressConcatenated option
> --------------------------------------------------------------
>
>                 Key: COMPRESS-220
>                 URL: https://issues.apache.org/jira/browse/COMPRESS-220
>             Project: Commons Compress
>          Issue Type: Improvement
>          Components: Compressors
>    Affects Versions: 1.4.1
>            Reporter: Gregory Chanan
>            Priority: Minor
>             Fix For: 1.5
>
>
> I want to use CompressorStreamFactory.createCompressorInputStream  to detect the compressor type for me and return the correct stream type, but I also want the stream to have decompressConcatenated turned on.
> I can check the type of the stream returned to me, use the two-arg constructor for that type and throw the original returned object away, but it would be simpler if there were either additional functions to do this for me in CompressorStreamFactory, i.e.:
> createCompressorInputStream(final InputStream in, boolean decompressConcatenated)
> createCompressorInputStream(final String name, final InputStream in, boolean decompressConcatenated)
> or through another Factory method, e.g. CompressorConcatStreamFactory.
> Thoughts?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira