[ https://issues.apache.org/jira/browse/IO-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568119#action_12568119 ]
David Smiley commented on IO-71: -------------------------------- I change my mind... a pair of parallel classes don't have access to the originating InputStream to close... nor do they know what particular IOException needs to get propagated forward. Perhaps you could have setters for these... but I think in the end, using these hypothetical pair of improved piped streams would result in code less natural to use than my PipedUtils. > [io] PipedUtils > --------------- > > Key: IO-71 > URL: https://issues.apache.org/jira/browse/IO-71 > Project: Commons IO > Issue Type: Improvement > Components: Utilities > Environment: Operating System: All > Platform: All > Reporter: David Smiley > Priority: Minor > Fix For: 2.x > > Attachments: PipedUtils.zip > > > I developed some nifty code that takes an OutputStream and sort of reverses > it as if it were an > InputStream. Error passing and handling close is dealt with. It needs > another thread to do the work > which runs in parallel. It uses Piped streams. I created this because I > had to conform > GZIPOutputStream to my framework which demanded an InputStream. > See URL to source. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.