There seem to be many links and other such stuff, but no actual code using pipes. The advantage of using java.io.PipedInputStream and java.io.PipedOutputStream is that there is no additional consumption of memory. ByteArrayOutputStream.toByteArray() returns a copy of the original buffer, so that means that whatever you have in memory, you now have two copies of … Read more
Note: This has been fixed in .Net Core 2.0. I’m not sure what is the status of the fix for .Net Framework. Calbertoferreira’s answer has some useful information, but the conclusion is mostly wrong. To create an archive, you don’t need seek, but you do need to be able to read the Position. According to … Read more
An InputStream ties up a tiny kernel resource, a low level file handle. In addition, the file will be locked to some extent (from delete, renaming), as long as you have it open for read. Lets imagine you didn’t care about the locked file. Eventually, if you need to read another file, and open it … Read more
You should always wrap the BufferedOutputStream with the ZipOutputStream, never the other way around. See the below code: FileOutputStream fos = new FileOutputStream(“hello-world.zip”); BufferedOutputStream bos = new BufferedOutputStream(fos); ZipOutputStream zos = new ZipOutputStream(bos); try { for (int i = 0; i < 10; i++) { // not available on BufferedOutputStream zos.putNextEntry(new ZipEntry(“hello-world.” + i + … Read more
char a = 0xab; cout << +a; // promotes a to a type printable as a number, regardless of type. This works as long as the type provides a unary + operator with ordinary semantics. If you are defining a class that represents a number, to provide a unary + operator with canonical semantics, create … Read more
Just because you use a buffer doesn’t mean the stream has to fill that buffer. In other words, this should be okay: public static void copyStream(InputStream input, OutputStream output) throws IOException { byte[] buffer = new byte[1024]; // Adjust if you want int bytesRead; while ((bytesRead = input.read(buffer)) != -1) { output.write(buffer, 0, bytesRead); } … Read more
Normally you should not close the stream. The servlet container will automatically close the stream after the servlet is finished running as part of the servlet request life-cycle. For instance, if you closed the stream it would not be available if you implemented a Filter. Having said all that, if you do close it nothing … Read more
/**Writes to nowhere*/ public class NullOutputStream extends OutputStream { @Override public void write(int b) throws IOException { } }
Assuming all the streams get created okay, yes, just closing bw is fine with those stream implementations; but that’s a big assumption. I’d use try-with-resources (tutorial) so that any issues constructing the subsequent streams that throw exceptions don’t leave the previous streams hanging, and so you don’t have to rely on the stream implementation having … Read more
You create and use byte array I/O streams as follows: byte[] source = …; ByteArrayInputStream bis = new ByteArrayInputStream(source); // read bytes from bis … ByteArrayOutputStream bos = new ByteArrayOutputStream(); // write bytes to bos … byte[] sink = bos.toByteArray(); Assuming that you are using a JDBC driver that implements the standard JDBC Blob interface … Read more