commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Smiley (JIRA)" <j...@apache.org>
Subject [jira] Commented: (IO-71) [io] PipedUtils
Date Wed, 13 Feb 2008 00:49:08 GMT

    [ https://issues.apache.org/jira/browse/IO-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568382#action_12568382
] 

David Smiley commented on IO-71:
--------------------------------

Jukka... I'm not going to tell you your code doesn't work, but it predictably suffers from
the problems I told you about (reference my paragraph starting with "The 2nd thread is a ...").
 Did you understand what I had to say?  If you need an example, I'll elaborate giving you
a hypothetical situation.  Perhaps in spite of these problems, it may be something that people
find useful provided that it's documentation heavily warn users of its limitations.  Personally,
I wouldn't use it.  Is requiring a thread to avoid these problem all that bad any way?

> [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, ReverseFilterOutputStream.patch
>
>
> 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.


Mime
View raw message