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

[jira] [Created] (IO-405) Support threshold=0 in ThresholdingOutputStream

Jochen Wiedmann created IO-405:
----------------------------------

             Summary: Support threshold=0 in ThresholdingOutputStream
                 Key: IO-405
                 URL: https://issues.apache.org/jira/browse/IO-405
             Project: Commons IO
          Issue Type: Improvement
          Components: Streams/Writers
    Affects Versions: 2.5
            Reporter: Jochen Wiedmann
            Assignee: Jochen Wiedmann
            Priority: Minor


I recently had a case where I would wish threshold=0 to trigger an immediate thresholdReached() in ThresholdingOutputStream(). This seems to me to be a natural expectation. However, thresholdReached() is only triggered after the first byte has been written.

I'd like to modify the constructor of ThresholdingOutputStream() in that sense. However, as thresholdReached() might throw an IOException, there are two possibilities I'd like to discuss:

1.) Pass the IOException through. Or, in other words: Modify the constructor to throw an IOException. (Slight binary incompatibility.)
2.) Catch the IOException, pass on a RuntimeException. Source code compatibility, but surprising for the developer.

Personally, I'm in favour for 1.)





--
This message was sent by Atlassian JIRA
(v6.1#6144)