3 ms·
> Wasabi is built to be 100% AWS S3 bit-compatible (same AWS API constructs for storage & identity management). No need to change your S3-compatible application
by throwaway2016a 9y ago
> Wasabi is built to be 100% AWS S3 bit-compatible (same AWS API constructs for storage & identity management). No need to change your S3-compatible application when using Wasabi
I often wonder how this works. With the whole Sun lawsuit with Google over the Java API making a clone of another platforms API sounds dangerous.
I'm curious what HN thinks.
I've wanted to have a "compatibility layer" that mimics my competitors APIs but have been scared of the possible repercussions.
- fasteo 9y agoThis. Would love to hear more about this.
- hedora 9y agoYou can't copyright a softwarw API in the US because they are considered purely functional (in the mechanical sense). Take flathead screwdrivers as an example. You can't copyright the dimensions of the blade head, since they're just the dimensions of the screw slot, and the only thing the copyright does is harm interoperability between screws and screwdrivers. You can copyright some other aspects of the screwdriver design, and if screwdrivers were a new thing, you could patent the idea of a screwdriver. This is why the Java case hinged on a former sun employee literally cutting and pasting method implementations he wrote at Sun into Android's implementation while he worked at google. /double-face-palm
- icedchai 9y agoIt wouldn't keep me up at night. Just do it.
- pella 9y agoMinio also has a S3 "compatibility layer" see: https://minio.io/ https://minio.io/ "implements Amazon S3 v4 APIs. Minio also includes client SDKs and a console utility."
- the_common_man 9y agohttp://pithos.io/ http://pithos.io/
- bdcravens 9y agoGoogle Cloud Storage does this (not sure about % of API completeness, but I've tested it with basic use cases like using Transmit) https://cloud.google.com/storage/docs/interoperability https://cloud.google.com/storage/docs/interoperability