tcpclient

I've pulled from several examples to setup a Full Duplex C# TCP Client connected to a server. The basic concept is that the client and server both send/receive messages (commands and events). Therefore, I've developed a FullDuplexSocket class that exposes a Send method to send messages to the server and a event handler to receive messages from the server. Everything works except I can't seem to flush the buffer of messages received from the server. Each time the server sends a new message, the buffer in my socket contains all the old messages (already read) and the new message(s). I could

I have problem with strange behavior of TcpClient.BeginConnect() and TcpClient.EndConnect() methods. I use BeginConnect() to add timeout to Connect() method (see extension method code below). If I get connected I call EndConnect() and every thing is ok, but If I get timeout I can't call EndConnect() because it will block for about 20 seconds, so I just call this non-blocking code: result.AsyncWaitHandle.Close(); result.AsyncWaitHandle.Dispose(); client.Close(); Problem is when I close the form right after getting timeout (after running above code) my app will "hang" for about 20 seconds. Is

I got a server that is managing two clients through NetworkStream.Read . Application protocol is: ClientMessage [128 Bytes] → Response from Server [128 Bytes] Now at server-side: Is it possible, that MyTcpClient.GetStream().Read() returns only < 128 Bytes, although all messages from client-side are exactly 128 bytes long? I guess that such a client message is short enough to fit into one packet on the tcp/ip layer - but could there be some kind of fragmentation or random although? Is NetworkStream.DataAvailable the right attribute to defend against this? After running smoothly for hours, i

I'm making a server - client program using TcpClient and server. To send from the server I use: static void send(string data) { sw.WriteLine(data + Environment.NewLine); } And when the client connects I'm sending some text: client = listener.AcceptTcpClient(); sr = new StreamReader(client.GetStream()); sw = new StreamWriter(client.GetStream()); string line; try { send("Hello world"); } //More code And to read from client: string data; data = sr.ReadLine(); if(data != string.Empty || data != null) { MessageBox.Show(data); } I tried putting inside while(true) and it froze, I tried putting inside

I'm trying to create a TCP Server & Client that will have a persistent connection so that the server and client at any point in time can notify each other of certain 'events'(so push instead of poll). I almost have everything working, clients can connect, connection is kept open and client and server can both write & read from the tcp stream. The problem is with the read, I've defined the message boundary by first sending 8 bytes that contain the length of the message. Once I've received it, the messages of lenght x is read and an event is raised. This all works fine but once the message has

while sending byte[] data via socket (a/sync) i'm getting on messagereceived event mismatch data. For example like this client: 2013-05-20 12:03:09.6929|DEBUG|Tcp|SendAsync_Completed: Sent ( ; T A , 59 84 65 13 10 ) to 127.0.0.1:10002 (Table)! 2013-05-20 12:03:09.8619|DEBUG|Tcp|SendAsync_Completed: Sent ( ; T A , 59 84 65 13 10 ) to 127.0.0.1:10002 (Table)! 2013-05-20 12:03:10.0249|DEBUG|Tcp|SendAsync_Completed: Sent ( ; T A , 59 84 65 13 10 ) to 127.0.0.1:10002 (Table)! 2013-05-20 12:03:10.1899|DEBUG|Tcp|SendAsync_Completed: Sent ( ; T A , 59 84 65 13 10 ) to 127.0.0.1:10002 (Table)! 2013-05