Investigate different ways of writing to stdout

[rm5248]

I came across this video the other day: https://www.youtube.com/watch?v=nH1YT1mrPt0
It's a faster(but much less flexible) way of doing logging.

The most important thing that I got out of it was the fact that the C library will do buffering. The lowest level that we do is to use fputs. This will go through the C library and use the builtin C library buffering.

Since we have the ability to buffer data in log4cxx already using a BufferedWriter, do a test to see if it would be faster to avoid the C library buffering and do a write() system call directly to write data out.

[swebb2066]

The lowest level that we do is to use fputs. This will go through the C library and use the builtin C library buffering

I believe the lowest level of Log4cxx is (usually) FileOutputStream::write which uses apr_file_write which:

1. obtains an OS dependent file lock
2. seeks to the end of the file
3. writes directly to the OS
4. releases the OS dependent file unlock

The above is 4-5 microsecs (as in the video) and happens once per logging request unless BufferedIO is set true. But as also mentioned in the video, debugging a crash when using buffered IO is a problem.