. Oktober 2021 18:29
An: dev@commons.apache.org
Betreff: Re: IO-753
Just a warning about threads: if this is to be used in Java EE, you are not
allowed to spawn your own threads. It would be better if the API can accept an
Executor or ExecutorService. That way, JEE applications can provide a
Utils.copy methods it would just be a shorthand for
a rather simple implementation. But one that the user can rely on to work
probably better than their own implementation.
-Ursprüngliche Nachricht-
Von: Rob Spoor
Gesendet: Samstag, 9. Oktober 2021 12:40
An: dev@commons.apache.org
Betreff:
rüngliche Nachricht-
> Von: Rob Spoor
> Gesendet: Samstag, 9. Oktober 2021 12:40
> An: dev@commons.apache.org
> Betreff: Re: IO-753
>
> Isn't this already possible with PipedOutputStream and PipedOutputStream?
>
> PipedInputStream inputStream = new Pip
: Re: IO-753
Isn't this already possible with PipedOutputStream and PipedOutputStream?
PipedInputStream inputStream = new PipedInputStream(size);
PipedOutputStream outputStream = new PipedOutputStream(inputStream);
Any write to outputStream is now visible in inputStream. Note tha
With
java.io.ByteArrayOutputStream, toByteArray() is needed, which copies the
data - unnecessarily in this case.
On 09/10/2021 10:44, sebastian.dietr...@e-movimento.com wrote:
Hi!
I'd like to contribute to https://issues.apache.org/jira/browse/IO-753
"Provide a IOUtils.copy(OutputStre
Hi!
I'd like to contribute to https://issues.apache.org/jira/browse/IO-753
"Provide a IOUtils.copy(OutputStream, InputStream)"
AFAIK this not possible without an extra thread which might be seen as too
"heavy" for commons-io.
So my question is: Is there any chan
