Initial stream of data may be ignored

[bparks13]

Since the socket needs to be connected before acquisition can begin, it is possible for the socket buffer to fill up before the user can start acquiring or recording data, leading to missed data. This is particularly true for large streams of data that exceed 64kB per packet.

One possible workaround:
Initialization of the socket can be started when acquisition begins (possibly inside startAcquisition()), which would increase the time between pressing the acquisition button and data appearing, but should ensure that no data is missed if the initial stream of data must be recorded.

To allow the GUI can start acquiring data successfully, however, the socket connection must be tested in the node prior to starting acquisition, since the node currently would not allow acquisition to start without an active connection. This could be accomplished by adding a checkbox to defer socket initialization until acquisition, to make sure that the socket is active and ready to receive a connection when acquisition begins.