Hi Phil
Actually, there was a long-standing latent bug in [net] where calls to
set the socket buffer size were effectively ignored, as they were
applied after the socket had been bound. This has recently been fixed
in the 2.0 branch head. See:
http://svn.apache.org/viewvc/commons/proper/net/branches/NET_2_0/src/main/java/org/apache/commons/net/SocketClient.java?r1=749145&r2=762023&diff_format=h
So, as Steve says, you can either make these changes locally, or just
download the latest source from the 2.0 branch and use that.
--Rory
On 22 Apr 2009, at 20:01, [email protected] wrote:
I have an ftp connection that would greatly benefit from having very
large TCP/IP window sizes (1MB). I'm having trouble figuring out how
to implement this using the standard FTPClient. What's the intended
usage of setReceiveBufferSize() and setSendBufferSize(), which are
inherited from the SocketClient?
From what I understand, setReceiveBufferSize() must be set prior to
binding to the socket? However, if these methods are called prior to
FTPClient.connect(), then this socket object isn't initialized.
After FTPClient.connect(), is it too late?
Any insight into configuring the FTPClient to configure these window
sizes is greatly appreciated.
Thanks,
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
