Tobias Rapp wrote: > http://support.microsoft.com/default.aspx?scid=kb;en-us;823764
By default winsock's send buffer size is 8 kb which is much bigger than TFtpCli's constant BLOCK_SIZE of 1460 bytes. So one condition described in the article is not true since a single send call in TFtpCli does not fill the whole underlying winsock send buffer. I realy wonder why disabling Nagle doesn't help? > > So shall I explicitly add a call setsockopt() that increases the > socket send buffer dramatically (>1MB)? Use WSocket option SocketSndBufSize instead, it will the call setsockopt() internally. I think that 1 MB is much too big, since this memory is allocated from kernel memory which is not an endless resource. --- Arno Garrels [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html What is your opinion about > that? > > /Tobias > > > -- > NOA Audio Solutions Vertriebsges.m.b.H. Tel: +43-1-5452700 > Johannagasse 42/4 Fax: +43-1-545270014 > A - 1050 Wien Www: http://www.noa- > audio.com -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
