Using inputStream.available() It is always acceptable for System.in.available() to return 0. I’ve found the opposite – it always returns the best value for the number of bytes available. Javadoc for InputStream.available(): Returns an estimate of the number of bytes that can be read (or skipped over) from this input stream without blocking by the next … Read more
BufferedReader can’t wrap an InputStream directly. It wraps another Reader. In this case you’d want to do something like: BufferedReader br = new BufferedReader(new InputStreamReader(is, “UTF-8”));
If all you want to do is read the same information more than once, and the input data is small enough to fit into memory, you can copy the data from your InputStream to a ByteArrayOutputStream. Then you can obtain the associated array of bytes and open as many “cloned” ByteArrayInputStreams as you like. ByteArrayOutputStream … Read more
That’s not possible in a portable manner in pure C++, because it depends too much on the terminal used that may be connected with stdin (they are usually line buffered). You can, however use a library for that: conio available with Windows compilers. Use the _getch() function to give you a character without waiting for … Read more
There are subtle differences as to how the fileName you are passing is interpreted. Basically, you have 2 different methods: ClassLoader.getResourceAsStream() and Class.getResourceAsStream(). These two methods will locate the resource differently. In Class.getResourceAsStream(path), the path is interpreted as a path local to the package of the class you are calling it from. For example calling, … Read more
As @substack corrected me in #node, the new streams API in Node v10 makes this easier: const Readable = require(‘stream’).Readable; const s = new Readable(); s._read = () => {}; // redundant? see update below s.push(‘your text here’); s.push(null); … after which you can freely pipe it or otherwise pass it to your intended consumer. … Read more
The goal of InputStream and OutputStream is to abstract different ways to input and output: whether the stream is a file, a web page, or the screen shouldn’t matter. All that matters is that you receive information from the stream (or send information into that stream.) InputStream is used for many things that you read … Read more
Use Apache Commons IO FileUtils.writeByteArrayToFile(new File(“pathname”), myByteArray) Or, if you insist on making work for yourself… try (FileOutputStream fos = new FileOutputStream(“pathname”)) { fos.write(myByteArray); //fos.close(); There is no more need for this line since you had created the instance of “fos” inside the try. And this will automatically close the OutputStream }
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
The shortest solution I know: using(var memoryStream = new MemoryStream()) { sourceStream.CopyTo(memoryStream); return memoryStream.ToArray(); }