> Then they get experience working with sockets... Ha. I have seen TCP sockets code which breaks in a "partial write" scenario, and even a "partial read" scen

> Then they get experience working with sockets... Ha. I have seen TCP sockets code which breaks in a "partial write" scenario, and even a "partial read" scenario. Code worked fine on their own LAN. Broke for someone else, they couldn't see why... They were very surprised when I explained that you don't always get one message per read(), because they had for years. Or maybe they hadn't, but assumed something else caused their occasional application glitches.