WOW! I have another prove for Buffering of Winsock! The used Memory is NOT increasing at alll! This means that the WINDOWS KERNEL is caching this!!! > > >> Ok, this proves that Winsocks is buffering megabytes of data before >> "TWSocket.pause" becomes active! >> > > Not quite correct, TWSocket.Pause becomes active immediately, however > winsock obviously continues to buffer incomming data, in this case I > think there's not much you can do and that won't be related to async > sockets IMO. TWSocket.Pause just stops winsock event notification. > > >>> Do you use LineMode? I do not think so but >>> should be asked anyway. If LineMode is turned on the component >>> indeed buffers data internally. >>> > > >> I am not using LineMode. If you look at TriggerDataAvailable you'll >> see that it never >> gaves the DoRecv in AsyncReceive a change to read. So I think it is >> proved that the >> problem is in Winsock, do you also think so? >> > > I doubt that it was a problem at all. Winsock does a lot of things in the > background you cannot control, even when the socket handle is already > closed. > > -- > 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
