I've noticed what appears to be a bug in the Socket.Receive method in the 1.1
Framework. Specifically, when talking between sockets on the same machine,
the Receive method appears to ignore anything after a newline. For example,
here is a snippet of server code listening on all local addresses:

IPEndPoint ipep = new IPEndPoint(IPAddress.Any, 8000);
Socket newsock = new Socket(AddressFamily.InterNetwork, SocketType.Stream,
ProtocolType.Tcp);
newsock.Bind(ipep);
newsock.Listen(10);
while (true)
{
try
  {
   // Wait for a connection request  
   Socket client = newsock.Accept();

   // more code to handle each connection on separate thread, etc
   }
}

and on the client side,

IPEndPoint ipep = new IPEndPoint(IPAddress.Parse("127.0.0.1"), 8000);
Socket server = new Socket(AddressFamily.InterNetwork, SocketType.Stream,
ProtocolType.Tcp);
Server.Connect(ipep);
etc.

These two apps will talk to each other on port 8000 without apparent
problems. If, however, a line of data is sent such as the following:

sent = server.Send(Encoding.ASCII.GetBytes("This is a \n line of data\r\n"));

then all bytes will be sent to the server app's socket, yet the
Socket.Receive call on the server end will only return up to the \n from the
local buffer. In other words it will only receive "This is a \n". If the
server app is written to wait for a full line of data terminated with \r\n
then it will hang indefinitely. This does *not* happen if the client app is
on a remote machine, only if it is running on the same machine as the server
app. This happens whether 127.0.0.1 is used or another IP on the local
machine.