{section: Socket connections that do not use class Sock}
StdUnivSock calls do_connect() (condor_util_lib/do_connect.c) to establish connection with the scheduler. Entire code path uses IPv4 specific constant and functions. Should I just convert them or introduce another socket class?
-Current Stream and Sock are somewhat bloated that it contains many different functions. In other words, it is not functionally coherent. Diverse functions are included in single class. The concept "Stream" is a feature of socket. It should be parent of Sock. This is where multiple interface inheritance kicks in. Consider "IStream" for the functionalities.
+Current Stream and Sock are somewhat bloated. It is not functionally coherent. Diverse functions are included in single class. The concept "Stream" is a feature of socket. It should not be parent of Sock. This is where multiple interface inheritance kicks in. Consider "IStream" for the functionalities. So, class Sock could remain just socket wrapper.
{section: Sinful string construction}
There are some places that construct sinful strings without using wrapper functions.
