Arno Garrels wrote: > If I were in your shoes I would at first search my application > for bottlenecks, lengthy blocking tasks, too small data chunks > sent/received etc.
When I search for issues I usually try to divide the area where the problem possibly exists into two parts and check both sides. If the problem can be excluded from one part I focus on the other part and try to divide it again. So in my current situation I want to find out if the problem comes from the sender side (data takes too long to generate) or receiver side (data takes too long to consume). Thus I hope to be able to take a look at the network buffer fill sizes to see if data is queued there or not. Do you know some other technique to sepearate the issue between server and client? Regards, Tobias -- 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