Hi, I've found this message in the Feb 2013 archives, and as I experience a similar problem (although in LineMode), I gave a try to the wsoNoReceiveLoop option.
Unfortunately, the problem still persists. I must add that, just before being stuck exactly like Robert below, so on the very previous DataAvailable event, what I receive is truncated - at the beginning of the string, and up to whatever character we use to separate the "command name" from is parameters (we tried both ':' and '|' separation characters, and whatever the size of what is before it, we lose it). We used TcpTrace between client and server to ascertain that everything was actually received from the client, and that's actually the case (even after DataAvailable stops firing). Example of truncated string: - expected string (and actually received when through TcpTrace): ****INFO:data1;data2;data3;data4... - received string (both with ReceiveStr or Receive function): :data1;data2;data3;data4... We tried different numbers of stars, and also the pipe instead of the colon, same behavior... Very weird... Any idea? Pascal Robert Dorn wrote: > Hello > > (sorry, my english is not soo good ;) ) > > I have a client and a server program and i use binary mode. The > communication between the both programs > works great. But after a few time one of the programs no longer call > the OnDataAvailable event. But still sending on both programs. the > program thats no longer call OnDataAvailable, has RcvdCount > 0 or > up to 8192. > > Any idea whats the problem are is? I guess you should include wsoNoReceiveLoop in the ComponentOptions property. -- -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
