Many miles data travel...

Recently I wrote to support team of one well-known data storage company with the problem: I can't read any of my files anymore from their servers after uploading them, however, it was working just fine a month ago with the same scripts. Let's learn guys from them how to reply to customers if something doesn't work... lol :)

I have replaced the company name, just to keep it more private...

***

Data being sent to or retrieved from [service] must often pass over many miles of network and through many network devices. Though unlikely for any given request, data loss or corruption in transit does occasionally occur. Fortunately, [our_company] provides a mechanism to detect this and retransmit the data.

[Service_name] REST PUT operation provides the ability to specify an MD5 checksum (http://en.wikipedia.org/wiki/Checksum) for the data being sent to [service]. When the request arrives at [service], an MD5 checksum will be recalculated for the object data received and compared to the provided MD5 checksum. If there's a mismatch, the PUT will be failed, preventing data that was corrupted on the wire from being written into [service]. At that point, you can retry the PUT.  

http://boonexpert.com
Quote · 13 Mar 2014
 
 
Below is the legacy version of the Boonex site, maintained for Dolphin.Pro 7.x support.
The new Dolphin solution is powered by UNA Community Management System.