3 ms·
What does this service do that can't be easily done by a client-side library? Also, S3 already has a REST API (see http://mashupguide.net/1.0/html/ch16s05.xhtm
by jluxenberg 16y ago
What does this service do that can't be easily done by a client-side library? Also, S3 already has a REST API (see http://mashupguide.net/1.0/html/ch16s05.xhtml http://mashupguide.net/1.0/html/ch16s05.xhtml ), you've just eliminated the URL signing bit.
- mleonhard 16y agoRestBackup keeps every application's data separate. Data uploaded through an access url can be downloaded only through the same access url. This is super useful for commercial software, since each user and license can have its own access url. To accomplish the same thing with S3, one would need to run a request signing service. RestBackup also prevents accidental and malicious deletions. The service keeps your data for the specified period of time no matter what.
- d2viant 16y agoInteresting points, so I would suggest emphasizing those more. Right now your page jumps right into API level stuff like URL's and curl commands. If I'm just glancing at your site nothing stands out as to why it's different than S3. I need to be sold on it before I ever get to the point of using those commands.
- blasdel 16y agoNone of the AWS 'REST' APIs are worthy of the name. While the S3 API is one of the less ugly ones, a bunch of it is crappily stateful and non-idempotent (like bucket creation).