I solved the problem on server side. I just found out a parameter ZNODELAY to configure my connection on the server (my server is writen in Mumps languague, running on Linux), and all works greate, even without using setsockopt on the client. I didn't think the problem could be on the server because when I run the same client program on Linux using Wine, it works without any delay.
Lukas Gebauer escreveu: >> I'm using the following lines to disable Nagle, but it's not working: >> >> FConnection.Connection.Connect(FConnection.Host, >> FConnection.Port); FConnection.Connected:=true; NoDelay:=True; >> >> setsockopt(FConnection.Connection.Socket,IPPROTO_TCP,TCP_NODELAY,@NoDe >> lay,SizeOf(NoDelay)); >> > > It should work fine, but your problem is probably not caused by > nagle. > > It is probably caused by 'delayed ACK'. In bad send-receive scenario > it causing 200ms delay. (see: your 100 send-receives * 200ms = your > 20 seconds.) > > What is your communication scenario? Does you have somewhere > something like: shortsend-shortsend-receiving sequence? (on client or > on server...) > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ synalist-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/synalist-public
