What I expect: flush() on the output stream to send the data. After flush() is completed, I expect the receiver to be able to read the data. Operating system and network may have their own delays - flush() is less than commit, so there is no guarantee that data is completely received, or it will ever be received when flush() is done, but it shouldn't be stuck in an intermediate java buffer with no way out until close().
.flush() documentation seems to match: 'forces any output bytes to be written out' and clarifies that if any bytes have been buffered, they should be written to their "intended destination
". And it clarifies that the OS may further buffer "the bytes are passed to the OS for writing
", and not that "they are actually written".
Let's take few examples: SocketOutputStream and FileOutputStream do nothing in flush() because they don't buffer anything, so write() will pass the bytes to the OS.
BufferedOutputStream is the best example of what to do when buffering: it does send all the bytes to the next stream in the chain AND calls out.flush(), so the data will go to the 'intended destination' - the buffer is just an intermediary. Well known that if you want any decent performance you should use BufferedOutputStream. Not so well known - you can use better buffers, for example one that doesn't reallocate and copy the byte, but instead keeps a list of buffers.
The biggest offender: DeflaterOutputStream
. Flush will just call out.flush()., but keeps recent bytes in its buffer. Worse - the actual Deflater
doesn't even support zlib flush
For Servlets, flush() does the right thing - the bytes go all the way to the net. Unless you're using compression, and the serlvet engine uses java Deflater - in which case flush() will not push bytes to the net, they get stuck in deflater. GZIPOutputStream extends Deflater and has the same problem - tomcat's coyote GzipOutputFilter and the example compression filter won't actually flush to the net.
The alternative for compressed output that flush() - http://www.jcraft.com/jzlib/
, BSD licence, pure java - has some good info about the flush() problem ). You can also use JNI
- Harmony's Deflater
is a good starting point - but Harmony has same bug as Sun VM