DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=31122>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=31122 FTPClient deals badly with adverse network conditions ------- Additional Comments From [EMAIL PROTECTED] 2004-09-09 18:29 ------- Regarding 1, isConnected is not supposed to notice if a connection has terminated abnormally. It is intended that one catch an exception in such a case. 4. The socket timeout is exactly that. If there's no activity on a socket for a given amount of time, it times out. The timeout happens in the TCP stack and java sets both SO_SNDTIMEO and SO_RCVTIMEO. 5. setDefaultTimeout is merely the socket timeout to set after a connection is established. There is no support for connection timeouts prior to J2SE 1.4, but Commons Net 1.2 is supposed to be J2SE 1.2 compatbile. If you want to set a connection timeout, you can create a socket factory as described in: http://www.mail-archive.com/[EMAIL PROTECTED]/msg07716.html --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
