Communication between Glish and clients is handled by a data transport layer called SOS .
Any necessary conversion is done at the receiving end of the communication.
This avoids unnecessary conversion on some architectures. The header portion of each event encodes information such as the architecture of the machine which sent the event, a time stamp, length of the event, etc. The header is followed by the actual event data. The header information and binary values are written to and read from SOS sinks and sources . Both of which can be found in Client.cc .