Socket Comm Followup - Timing Out

[Brian Yennie]

Any chance you're not reading all of the data on the first pass, 
perhaps missing some white space or not swallowing up the terminator 
itself? I don't _think_ you should get a timeout if there aren't any 
reads or writes pending, although I could be wrong.

Of course as long as the socket isn't closed after the timeout, it 
shouldn't much matter...

> OK, I have everything working fine now, with a timeout question:
>
> After one app finishes talking to the other, after a couple of seconds 
> both
> apps register a socketTimeout... however if I come back and send data 
> from
> either app, it is received properly, so should I be concerned about the
> timeout?