Changes between Version 30 and Version 31 of SftpFrontend


Ignore:
Timestamp:
2010-06-13T19:13:17Z (14 years ago)
Author:
davidsarah
Comment:

WinSCP workaround

Legend:

Unmodified
Added
Removed
Modified

  • SftpFrontend

    v30 v31  
    1212=== General compatibility issues ===
    1313
    14 Before uploading a file to a Tahoe filesystem, the whole file has to be available. This means that the upload can only start when the file has been closed in the SFTP session. Particularly when writing large files, the client may time out between sending the close request and receiving the response (ticket #1041). This is known to be a problem for at least the WinSCP client, which has a close timeout of 15 seconds.
     14Before uploading a file to a Tahoe filesystem, the whole file has to be available. This means that the upload can only start when the file has been closed in the SFTP session. Particularly when writing large files, the client may time out between sending the close request and receiving the response (ticket #1041). This is known to be a problem for at least the WinSCP client, which has a default close timeout of 15 seconds. In the case of WinSCP this can be worked around by setting WinSCP -> Connection -> Timeouts to 6000 seconds (the maximum allowed); other clients with this problem may have similar settings.
    1515
    1616In the period after the close but before the upload has finished, the closed file may not appear in directory listings, or may appear with an incorrect modification time.