[
https://issues.apache.org/jira/browse/IO-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved IO-382.
---------------------
Resolution: Fixed
Fix Version/s: 2.5
URL: http://svn.apache.org/r1489238
Log:
IO-382 Chunked IO for large arrays
Added:
commons/proper/io/trunk/src/main/java/org/apache/commons/io/output/ChunkedOutputStream.java
(with props)
commons/proper/io/trunk/src/main/java/org/apache/commons/io/output/ChunkedWriter.java
(with props)
Modified:
commons/proper/io/trunk/src/changes/changes.xml
commons/proper/io/trunk/src/main/java/org/apache/commons/io/IOUtils.java
> Chunked IO for large arrays
> ---------------------------
>
> Key: IO-382
> URL: https://issues.apache.org/jira/browse/IO-382
> Project: Commons IO
> Issue Type: New Feature
> Components: Utilities
> Reporter: Sebb
> Fix For: 2.5
>
>
> File IO involves native code at some point.
> It seems that native code which accesses a Java
> array may involve copying the array (depending on the JVM) [1]
> This can easily lead to an OutOfMemory condition if the array is large.
> It would be useful to provide some utility methods to process the array in
> chunks of (say) 4K. It's unlikely that applications will use huge read
> buffers, but they may well need to write large buffers, so only output
> chunking is likely to be useful.
> It might also be useful to create a ChunkedOutputStream/Writer which provides
> the chunking automatically.
> [1]
> http://docs.oracle.com/javase/7/docs/technotes/guides/jni/spec/design.html#wp1265
--
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
