Hi. I'm using FTPClient.retrieveFileStream() and therefore I need to implement keepalive mechanism by my own.
I wanted to mimic the implementation from FTPClient.CSL, but then I thought: Most FTP servers don't reply to NOOPs until transmission has finished and yet, sending NOOPs helps to keep them alive. So we can safely assume that no FTP servers support this and let CSL.cleanUp() collect all the responses at the end. My tests show vsftpd 2.2.2 does not support that and you can send up to 27000 NOOP commands to it until the socket write gets blocked. On the other hand, on most FTP servers for each NOOP keepalive FTPClient waits for 1000 milliseconds for a reply that never comes. This slows things down a little. What bad thing will happen, if we remove __getReplyNoReport() from FTP.__noop() and increment notAcked unconditionally? --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
