Found if --without-x was specified, that automatically caused an
error condition in the configure script. Fixed that and only
tested for X windows headers and libs if X is included. Excluded
a couple of directories from compiling if X is not included.
Didn't seem to be a problem with java.
Removed checks on dead units conversion messenger. Units conversion
messages cannot be suppressed. Added deprecated messages to the functions
that modified the message printouts.
If we are on a Mac, use xcrun to find the standard include directories.
Some of the makefiles in data_products look for libxml2 which requires
them to get the same change as the configure script.
* Fix endl issue in variable server JSON generation. Ref #766
* Change std::endl to line feed as appropraite. #766
* Change std::endl to line feed in MemoryManager as appropriate. #766
* Change std::endl to linefeed as appropriate. #766
* Change std::endl to line feed as appropriate in JSONVariableServer. #766
* Change std::endl to line feed as appropriate in still more files. #766
std::endl flushes the output stream. The SIE functions were using it
multiple times per variable. This can have significant performance
impacts on file I/O.
In testing, the S_sie.resource file for SIM_parachute was flushed over
14000 times, each resulting in a separate write system call. With this
patch, only ~40 write calls were performed, and writing the file took
~1/3 as long.
For more information, see
https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#Rio-endl
If real-time is off, we exit the rt_monitor function early. The frame
scheduled time was calculated after the exit call. Moved the frame
scheduled time calcuation before the exit.
* Add capability to list current variable server connections in JSON ref #678
* Add client tag to the connection info.
* Name consistency tweak in generation of JSON variable-server connection list. ref #732
* Add client IP address and port. ref #732
* Output should be going to the stringstream, not std::cout. Ref #732
The TCP_NODELAY socket option disables Nagle's algorithm on TCP sockets,
improving latency at the cost of throughput. This option is
TCP-specific, and it is an error to use it on any other kind of socket,
including UDP. It is also unnecessary, since UDP is datagram-based and
does not buffer data to be transmitted.
We know how many more elements we are going to push into ```listLogGroupIterators_``` so use that to our advantange and reserve inadvance to save on re-allocation costs.
