[Cyberduck-trac] [Cyberduck] #5186: Perform MD5 hash calculation during upload
Cyberduck
trac at trac.cyberduck.ch
Mon Sep 13 18:24:12 CEST 2010
#5186: Perform MD5 hash calculation during upload
----------------------------------------------------------------------------------------------+
Reporter: https://www.google.com/accounts/o8/id?id=aitoawnnvt-90frc5_hjyhabpzmeshpw03k3snc | Owner: dkocher
Type: enhancement | Status: new
Priority: low | Milestone:
Component: s3 | Version: 3.6.1
Severity: minor | Keywords:
Platform: | Architecture:
----------------------------------------------------------------------------------------------+
Currently a MD5 hash of every upload to S3 is calculated before starting
the upload. This can consume a large amount of time and no progress bar
can be given during that operation therefor the upload time estimate is
useless.
I suggest to calculate the MD5 hash during the upload when reading from
the stream. See for an example: http://stackoverflow.com/questions/304268
/using-java-to-get-a-files-md5-checksum
Now S3 will not return an error for a corrupted upload since it has no
hash to compare. Instead the returned ETag from S3 has to be used to
verify that the upload was successful:
http://docs.amazonwebservices.com/AmazonS3/latest/API/RESTObjectPOST.html
Alternatively it would be good to have at least the option to disable the
hash computation since there are cases where the overhead is not
justified.
--
Ticket URL: <http://trac.cyberduck.ch/ticket/5186>
Cyberduck <http://cyberduck.ch>
FTP, SFTP, WebDAV, Cloud Files, Google Docs, Azure and S3 Browser for Mac OS X.
More information about the Cyberduck-trac
mailing list