[Cyberduck-trac] [Cyberduck] #8182: Failure to retry transfer with network failure

Cyberduck trac at trac.cyberduck.io
Wed Oct 28 09:23:36 UTC 2015


#8182: Failure to retry transfer with network failure
--------------------------+-----------------------
 Reporter:  FiFtHeLeMeNt  |         Owner:
     Type:  defect        |        Status:  closed
 Priority:  normal        |     Milestone:  4.5.2
Component:  core          |       Version:  4.5.1
 Severity:  normal        |    Resolution:  fixed
 Keywords:                |  Architecture:
 Platform:                |
--------------------------+-----------------------

Comment (by dkocher):

 Replying to [comment:7 dkocher]:
 > Replying to [comment:5 FiFtHeLeMeNt]:
 > > Hi David ,
 > > Is there any particular reason for not implementing keep alive
 function ? because even if you fix "Try Again" option, it means cyberduck
 will hang for 5-10 seconds until it detects there is something wrong with
 connection and then try to re-establish the connection which includes all
 authentication and so on which is another 5 seconds. it means every save
 will take 10-15 seconds. Why not to prevent the problem instead of trying
 to fix it every time ?
 > > connection keep alive is standard feature of good FTP clients and
 other similar products like webdrive already have this feature.
 >
 > We will consider adding an idle connection check for FTP connections.
 This is already implemented for SFTP with version 4.5.

 Now in #9075.

-- 
Ticket URL: <https://trac.cyberduck.io/ticket/8182#comment:10>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows


More information about the Cyberduck-trac mailing list