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 21:45 ------- The root of the problem is the nasty telnet code. As I indicated on commons-dev in response to a related issue: I think the long term solution should be to branch, leaving the 1.2 series as J2SE 1.2 and 1.3 compatible, and reimplement telnet using selectable I/O in a single thread on the head branch; or start a new 2.0 branch either as a branch or in the sandbox as commons-net2, since everything would have to be overhauled once we start using java.nio. Basically, I think we're seeing enough user demand that we should contemplate the move to J2SE 1.4, even if we have to maintain two separate branches (although I prefer the commons-net2 approach). I think we've taken incremental patching as far as we can. On a separate note, the whole isConnected behavior issue needs to be sorted out in a 2.0 version. There has been enough of an expectation from users as far as FTPClient is concerned for it to report the current state of the underlying socket. Previous to J2SE 1.4, it was not possible to to test that state. But Socket.isConnected and SocketChannel.isConnected were added in J2SE 1.4, so that is what a future SocketClient.isConnected should return. Keep in mind that you should be able to subclass FTPClient and override isConnected if you're using J2SE 1.4 to return Socket.isConnected (I think). --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
