mfisc...@bfe.tv wrote: > Hi, > i am using the Standard TWSocket in a Server and round about 70 > Clients. After a Client is connected to the Server, the Client starts > immediately to send string messages. After some sort of filtering the > messages are broadcasted to a subset of all connected Clients. > Especially at start up some clients send up to 10.000 messages with > an average size of 40 bytes.
Have you already tried to include wsoNoReceiveLoop in client objects' ComponentOptions? Also are those large amount of socket messages sent in a blocking loop? If so, change that to send the next message when the previous one actually has been sent, that is when event OnDataSent triggers. > Sometimes it happens, that in the Server the OnDataAvaiable-Callback > stops to be triggered. > If i call receive(nil,0) on the affected socket, everything gets back > working correctly. > In my opinion some postmessage-calls in the socket are discarded > because the windows message queue for the server process is full. > If i set HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows > NT\CurrentVersion \Windows\USERPostMessageLimit to Value of 50.000 > Everything seems to be working fine. IMO TWSocket should be changed to raise an Exception if a call to PostMessage() fails, currently it doesn't check the PostMessage() return value. -- Arno Garrels -- 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
