3 ms·
Not sure if I missed it in the API documentation but what happens if I PUT a file with a file name that already exists? One thing that drives me nuts about a l
by IgorPartola 16y ago
Not sure if I missed it in the API documentation but what happens if I PUT a file with a file name that already exists?
One thing that drives me nuts about a lot of backup services is that they say that the data is encrypted. It is important to recognize the two places where data can be intercepted:
* In transport, unless it's done over TLS/SSL. Most services provide this.
* Once stored. This is done very rarely and if it is done, the provider is the one that has the encryption key.
With your service you can actually take care of both by simply instructing your users to encrypt the file before uploading it.
Another bits of functionality I'd say you are missing are "diff" backups. I don't necessarily want to upload my entire 300GB multimedia library each day when I want to back it up (especially if I'm being charged for traffic). I'd rather upload a small diff.
A very cool use of this technology would be a FUSE plugin for browsing your storage area.
- mleonhard 16y agoHi Igor, thanks for your comment. If you PUT a file that already exists, you'll get a 405 Method Not Allowed error. With the right software, you could keep track of what is already uploaded and compute a diff locally on your computer. When uploading a diff, you would want to extend the expiration of the previously uploaded files. I'm open to suggestions for how to add this to the API. The httpfs FUSE plugin should work with RestBackup. I can fix it if it doesn't work. Would you like to sign up for the alpha-test and give it a try?