Cyberduck Mountain Duck CLI

Changes between Initial Version and Version 1 of Ticket #5396, comment 10


Ignore:
Timestamp:
Nov 4, 2010 2:45:04 PM (11 years ago)
Author:
dkocher
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #5396, comment 10

    initial v1  
    1 That may well be the answer to 5395 (which is indeed a duplicate of 5308, except on Windows instead of Mac), but this ticket is about why the software does not correctly report the issue.  The folder is shown as empty, not faulty.  If there is an error in the data being returned from the server, you should say there is an error and say what it is, not incorrectly show the folder as empty.
     1That may well be the answer to #5395 (which is indeed a duplicate of #5308, except on Windows instead of Mac), but this ticket is about why the software does not correctly report the issue.  The folder is shown as empty, not faulty.  If there is an error in the data being returned from the server, you should say there is an error and say what it is, not incorrectly show the folder as empty.
    22
    3 As far as I am concerned, the inability to report an error is far more serious than the failure to handle it - which is why this ticket was flagged as higher priority than 5395.  Once we get the client telling us what it thinks the error is, we can ask the server supplier to fix it.  As Cyberduck is the only client which thinks this is an error, we cannot use another client to generate the report so the server supplier just ignores our requests.
     3As far as I am concerned, the inability to report an error is far more serious than the failure to handle it - which is why this ticket was flagged as higher priority than #5395.  Once we get the client telling us what it thinks the error is, we can ask the server supplier to fix it.  As Cyberduck is the only client which thinks this is an error, we cannot use another client to generate the report so the server supplier just ignores our requests.
    44
    55Regards